THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
S U M M A R Y
DIARY: June 15, 2000 04:00 PM Thursday;
Meeting on Bootstrap OHS/DKR project at SRI.
2...Events, Introductions - Diverse Skills Focused on DKR Project
3...Attendance of Meetings Open
4...Organizational Platform Sought; SRI Aids Funding Outreach
5...Project "Plan" to Attract Sponsors Must Show Ability to Perform
6...Meeting Agendas Set by Doug Engelbart; Need Schedule for Priority
7...Video Conferencing, Audio Broadcasting DKR Meetings at SRI
8...DKR Project Must Transition Toward Knowledge, Away from Pictures
9...Bootstrap Development Strategy Requires Scheduling Tasks
10...Vector Sets OHS as Foundation of Project
11...Organization (Platform) Needed to Take Over Project Operations
12...Follows Program Invites Prominent People to Address SRI Team
13...Sponsors Looking for Projects in Knowledge Management
....Mozilla Enthused About OHS
....Gnutella Presentation Can be Scheduled
....Doug/Pat Presentations for DARPA Next Week on Using Internet
....SPC Workshop for DARPA on Applying Internet; Doug/Pat to Present
....DOD Contacted Doug on DKR Opportunities
....Sun Needs OHS Long Term, Wants Better Hardware Design Tools
....Demo Project Deliverable Aids Sponsor Outreach
....Funding Requires Initial Project Development
....Funding Requires Proof of Concept, Not High Tech "Tourism"
....Summarize Project Support Funding Inquiries for DKR
....Audience for Sponsor Funding is Government Agencies
14...Multiple Views, Storyboard Features
15...Software Programming Multiple Views, Storyboard Features
16...Programmers Initial Target Community Supports Bootstrapping
17...Backlink Management Developed by Doug's Colleague Pending Review
18...Email Addressability Needed to Aid Project, Demonstrate Progress
19...Separate Mailing List on Development of OHS, Possibly SourceForge
20...Server Space for DKR Donated by Sun Microsystems
21...Legal Issues Arising from Open Source and Sponsor Support
....Open Source Evidence Showing Viability of Development Strategy
....Study Cost Benefits of Open Source
....Management Assignments Difficult to Make under Open Source
22...DKR Project Knowledge Management Objective, Beginning with OHS
23...OHS Same as CDS Requirements Prepared by Eric Armstrong
24...What Are We Trying to Accomplish Knowledge Management Beyond Reach
25...Lesson Learned Not Enough Known about Knowledge and KM for DKR
26...Knowledge Management Not Well Enough Understood to Develop DKR
....Knowledge Management Definition
....OHS Editor Based on XML Initial Project Deliverable
....Collaborative Document System and OHS Supported by Editor
....CDS Change to OHS; Requirements Need Review by Project Team
....Bootstrap Alliance Tech Template Project 0 OHS Framework
....Atomic Data Structures Derive from Fundamental Information Unit
....Fundamental Information Unit Focuses DKR Design Effort
....Mind Maps, Concept Graphs Facilitate Use Case Analysis
....Use Case Methods for Software Design and Email Addressability
27...Glossary Establishes DKR Culture, Supports Architecture for KM
.....Primary Glossary Supported by Separate Page for Each Term/Phrase
28...Augment Project at SRI in 1960s Sets Design Objectives
29...Video of Augment Will Demonstrate OHS/DKR Objectives
30...Augment Needs Review for Data Structures Incorporate into OHS
31...Guide to Running NICs Gathers Intelligence, Provides Feedback
32...Communication Manager Proposed to Compliment Tools for DKR
33...Current Proposal for DKR Transcoding - Complex Process
34...Architecture - Three-Tier Server for WBI Implementation
....Eugene and Rod Have DKR Systems
....Hitchiker's Guide To The Galaxy Good Example DKR
....Fundamental Issues of DKR Project Focused by DOM
....DOM (Document Object Model) Uses XML for Doc Management
....Augment Data can be Transcoded
....Evaluate Starter Technologies, Volunteers
....Pilot Test Wiki for DKR Collaboration
....Starter Technology Pilot Testing Wiki for Better Collaboration
....Wiki Addressable Email Enhances Project Collaboration
....Accountability - Requires Social Contract
....Members Setup Homepage for Comments, Nobody Changes Anything
....Prototype Email Enhancement for Collaboration
....Collaboration, Prototype Enhance Email
....Engineering Management Requires Procedures, Accountability
Click here to comment!
1...Develop basic XML schemes for what we're doing, can generate html
2...A Gnutella presentation can be scheduled for one of our meetings.
3...Eugene seemed to indicate the Open Source study would be ready
4...Need an example of relying on intuitive idea of "knowledge"?
0201 - Bootstrap Institute
020101 - Mr. Douglas C. Engelbart, Ph.D.
0202 - Sri International
020201 - Mr. Lee Iverson
0203 - Sri International
020301 - Mr. Pat Lincoln; 650 859 5454
OHS/DKR Meeting at SRI 000518
0403 - ..
0404 - Summary/Objective
040501 - Follow up ref SDS 66 0000, ref SDS 60 0000.
040503 - Gil Regev visiting team member from Switzerland demonstrated strong
040504 - flow charting for concept mapping that can aid development of use
040505 - cases. ref SDS 0 6864 Need project schedule to identify priority for
040506 - performing a wide range of tasks. ref SDS 0 4745 Making progress on
040507 - OHS vector, ref SDS 0 3855, and on developing prototypes to demo
040508 - project capabilities for sponsor fund raising. ref SDS 0 6821
040509 - Progress on Doug's request for better email to collaborate, Wiki
040510 - system up and running. ref SDS 0 2760 Might lead to separate
040511 - communication channel to expedite development. ref SDS 0 5985 Issues
040512 - on licensing deferred another week; study on open source pending.
040513 - ref SDS 0 3055 Focus in near term is on OHS; deferring work on
040514 - knowledge management until more experience is gained. ref SDS 0 6271
040515 - Review of OHS Requirements to identify initial development scope is
040516 - pending. ref SDS 0 5880 Good progress on Use Case work, needs
040517 - coordination with Requirements. ref SDS 0 4933
040519 - [On 000616 received minutes of meeting from Su-Ling Yee.
040520 - ref SDS 70 0001
DKR Project Staff
SourceForge Lecture on 000630,
0706 - Discussion
070701 - ..
070702 - Events, Introductions - Diverse Skills Focused on DKR Project
070704 - Follow up ref SDS 66 2079, ref SDS 60 2079.
070706 - Doug Engelbart
070708 - Will do an internal lecture for Source Forge on Friday, 000630.
070709 - ref DRP 13 8464
070713 - ..
070714 - Guests...
070715 - ..
070716 - Gil Regev
070718 - From the Swiss Federal Institute in Lucerne, Switzerland: which
070719 - has been part of the Bootstrap Alliance for 3+ years. Gil works
070720 - on component oriented software engineering, and doing a PhD on
070721 - collaborative learning.
070722 - ..
070723 - Knoware Demonstrated
070725 - Today, Gil demoed Knoware - a concept map editor he developed to
070726 - support collaboration. ref DRP 13 6279 and ref DRP 13 3960
070728 - Knoware provides advanced flow diagraming, similar to CPM, but
070729 - aimed at mapping of generic ideas and building concepts. A key
070730 - advance is effective management for collaborative contributions.
070732 - ..
070733 - Might be useful for use case analysis, per below. ref SDS 0 4933
070735 - ..
070736 - Possibly Gil when a few use cases are ready, Gil could pop them
070737 - into his program to demonstrate the application, per Doug's plan
070738 - on 000326 to use the project record to develop the tools,
070739 - discussed below by Eugene on Bootstrap strategy. ref SDS 0 9622
070741 - [On 000621 received minutes of meeting from Su-Ling Yee.
070742 - ref SDS 71 0001
070744 - ..
070745 - [On 000622 Eugene Kim cited Gil's Knoware program during the
070746 - meeting at SRI while discussing catagories for links.
070747 - ref SDS 73 3808
070750 - ..
070752 - ..
070753 - Attendance of Meetings Open
070755 - Gil Regev expressed appreciation for the opportunity to attend
070756 - the meeting today.
070758 - There was discussion that DKR project meetings at SRI are open, so
070759 - that extended team members are welcome to attend when convenient,
070760 - as in Gil's case where he has a scheduled meeting in Los Angles,
070761 - and so stopped in the Bay Area, making it possible to attend the
070762 - meeting today.
070764 - ..
070765 - Eugene will discuss policy of openness for meetings with Doug.
070766 - ref DRP 13 4662
Planning, Objectives, Schedule, Budget, Agenda Issues
SRI Organizational Platform, Project Management
Management and Governance
Iverson, Lee Assigned Full Time by SRI
Lincoln, Pat (SRI) Assisting on Sponsor Outreach for Funding
190901 - ..
190902 - Organizational Platform Sought; SRI Aids Funding Outreach
190903 - Project "Plan" to Attract Sponsors Must Show Ability to Perform
190905 - Follow up ref SDS 66 0784, ref SDS 60 0784.
190907 - No discussion of Millennium project for organizational platform
190908 - discussed on 000601. ref SDS 60 1624
190910 - ..
190911 - Pat Lincoln and Lee Iverson supporting project under SRI participation
190912 - reported during the meeting on 000601. ref SDS 60 1760
190913 - ..
190914 - Nothing tasked today on developing a schedule, budget, staff
190915 - requirements and management manual per planning on 000324, ref SDS 18
190916 - 2640, to demonstrate ability to perform, reflecting reliance on SRI
190917 - and/or other agency for organizational platform, reviewed on 000601.
190918 - ref SDS 60 1575
190920 - [...below, Eugene identifies activities that need to be scheduled,
190921 - as part of Bootstrap strategy. ref SDS 0 9622
190925 - ..
190926 - Meeting Agendas Set by Doug Engelbart; Need Schedule for Priority
190928 - Follow up ref SDS 66 4455, ref SDS 60 4455.
190930 - On 000531 Eugene requested suggestions of agenda issues for weekly
190931 - meetings, and recalled today receiving ideas, ref SDS 58 0001,
190932 - following up Eric Armstrong's similar request on 000407. ref SDS 23
190933 - 6554
190935 - ..
190936 - Gil Regev, visiting project contributor from Switzerland, ref SDS 0
190937 - 2079, asked if anyone can submit agenda issues to expedite progress?
190938 - ref DRP 13 2440
190940 - ..
190941 - Eugene encouraged all contributors on the project, including members
190942 - of the extended team who are unable to attend weekly meetings, to
190943 - submit ideas for agenda issues, and comments on the work being
190944 - reported, ref DRP 13 7030, as set out in the record of the first
190945 - meeting on 000324. ref SDS 18 2563
190946 - ..
190947 - This aligns with Doug Engelbart's presentation on the Guide
190948 - to Running Nics, on 000427 which impliedly requires collaboration
190949 - by all contributors in order to develop effective "intelligence"
190950 - for maintaining progress of the work. ref SDS 37 2867
190952 - ..
190953 - Agenda issues typically are controlled by progress of the work, with
190954 - priority set by the schedule and pending action items to implement the
190955 - schedule, shown in the meeting on 000324, per above. ref SDS 0 4745
190956 - For example, on 000601 Marcello Hoffman proposed an action item to
190957 - identify "hooks" that attract funding. ref SDS 60 4080 Progress on
190958 - this action item comprises a meeting "agenda" issue.
190960 - ..
190961 - Eugene explained today that meeting agendas are based on discussion
190962 - with Doug Engelbart. Eugene reviews issues with Doug and publishes an
190963 - agenda based on that discussion. ref DRP 13 4070
190965 - http://www.eekim.com/ohs/agendas/
190966 - ..
190967 - The disposition of pending issues is not clear in the record.
190969 - ..
190970 - Eugene will submit an email once a week requesting proposed agenda
190971 - items. After reviewing issues with Doug, Eugene will prepare an
190972 - agenda and upload to a web address. He will send an email to the team
190973 - notifying that the agenda is available, with a link to the location.
190974 - ref DRP 13 5538 and ref DRP 13 3008
190976 - This procedure provides a record of suggested agenda issues, and
190977 - those that are adopted. It can be supplemented by maintaining a
190978 - list of pending action items, so that the correlation between
190979 - pending work and proposed agendas is maintained within span of
190980 - attention. Once a schedule is developed and an action item system
190981 - is in place, these can begin controlling the work.
190982 - ..
190983 - This record helps develop Guide to Running Nics, per below.
190984 - ref SDS 0 3995
Remote Staff Participation
Video, Audio Broadcast SRI Meetings
Video Audio Broadcast Meetings at SRI
230701 - ..
230702 - Video Conferencing, Audio Broadcasting DKR Meetings at SRI
230703 - DKR Project Must Transition Toward Knowledge, Away from Pictures
230705 - Follow up ref SDS 66 5094.
230707 - Eugene mentions the possibility of audio conferencing weekly meetings
230708 - at SRI, ref DRP 13 2115, following up discussion of this subject
230709 - during the meeting on 000608, when the matter was tabled. ref SDS 66
230710 - 4757
230712 - ..
230713 - Eugene advises that all list subscribers are welcome to stop by when
230714 - in the area. Most Open Source projects don't happen face-to-face
230715 - meetings, primarily because much of the difficult conceptual work is
230716 - already accomplished. Open Source typically implements established
230717 - methods like an operating system, email, a web browser, search engine,
230718 - etc. This kind of work can mostly be accomplished online.
230719 - ..
230720 - Knowledge Management requires a conceptual breakthrough, as seen
230721 - below discussing a direction for development. ref SDS 0 6271 As a
230722 - result, a DKR project in the beginning requires a stronger level of
230723 - collaboration, as reported on 991217. ref SDS 9 9540
230725 - ..
230726 - Eugene emphasized today that this issue is important in future, when
230727 - there is code base, requirements, etc. Once we reach the point of
230728 - design implementation we will shift to being online. ref DRP 13 6150
230730 - ..
230731 - On 000324 methods of involving remote contributors by reliance on the
230732 - project record, were set out. ref SDS 18 2563 A DKR project must move
230733 - toward reliance on the record, and away from video conferencing for
230734 - the reasons on 991222. ref SDS 10 3908
Bootstrap Strategies, 000227
Pilot Test Prototype Methods Using Project Record
Case Study Project Meetings Pilot Test Prototype Tools, Methods, 00032
Bootstrap Strategy Pilot Test Prototype KM with Project Record
270801 - ..
270802 - Bootstrap Development Strategy Requires Scheduling Tasks
270804 - Follow up ref SDS 52 3604, ref SDS 45 4514.
270806 - Eugene reviewed Bootstrapping strategy - doing bottom up things while
270807 - top down stuff is being discussed. ref DRP 13 6474
270809 - On 000406 Bootstrap strategy beginning with software development
270810 - explained during meeting at SRI. ref SDS 22 5078
270812 - ..
270813 - On 000509 Paul Fernhout reviewed Bootstrapping. ref SDS 45 4514
270815 - ..
270816 - On 000614 Eric Armstrong provided link to Bootstrap priorities
270817 - which sets building DKR with bootstrapping. ref SDS 69 8954 Eric
270818 - explains development issues that complicate developing software
270819 - programming. ref SDS 69 5826
270820 - ..
270821 - Bootstrap benefits for software programming shown in reviewing
270822 - Eric's letter on 000614, not reviewed today. ref SDS 69 1650
270824 - ..
270825 - Develop basic XML schemes for what we're doing, can generate html
270826 - automatically and build in the features Doug wants. Helps us focus,
270827 - refine our thoughts about building DKR. ref DRP 13 1287
270829 - ..
270830 - Develop basic XML schemas for current docs. Find existing DTDs, Howard
270831 - has found a Minutes DTD. Once we commit to a license will put any of
270832 - our own created schema into Open Source under the group license.
270833 - Xpointer, Xlink, Xinclude---link of Joe's wiki glossary---everyone
270834 - should study it for xml knowledge. ref DRP 13 3705
270836 - [...below, Lee has placed the glossary in Wiki.
270837 - ..
270838 - These are tasks that need to be scheduled, per planning on
270839 - 000324, ref SDS 18 7482, and discussed above under PM. ref SDS 0
270840 - 4745
270842 - ..
270843 - Neil Bradley, The XML Companion, 2nd Edition. Martin Fowler, UML
270844 - Distilled, 2nd edition. John points out John Bosack would be a good
270845 - person to point us in the right direction. ref DRP 13 6708
270847 - ..
270848 - Minutes, agendas, glossary, use cases/requirements give us content
270849 - that can be sucked into the system. ref DRP 13 6880
270851 - Aligns with Doug's strategy reported on 000326 to use the project
270852 - record for pilot testing prototype capabilities. ref SDS 19 5972
270854 - [...below, concern expressed about slowness of Bootstrap to
270855 - disclose process of KM, even though Wiki web site has only been
270856 - active a few days. ref SDS 0 6271
OHS Primary Objective, Doug, Marcello, 000601
Organizational Platform, Millennium, Doug
Management and Governance, Accountability
Fellows Program, Doug
DKRs Build, Doug, Marcello, 000601
SRI Organizational Platform, Project Management, 000419
Vector Task Priorities, 000601
Millennium Project Organizational Platform, 000601
391101 - ..
391102 - Vector Sets OHS as Foundation of Project
391103 - Organization (Platform) Needed to Take Over Project Operations
391104 - Follows Program Invites Prominent People to Address SRI Team
391106 - Follow up ref SDS 66 3855, ref SDS 60 3855.
391108 - Progress on vectors set by Doug on 000601...
391110 - 1. OHS is foundation of the project effort so far, reported vector
391111 - on 000601. ref SDS 60 3855
391113 - ..
391114 - Schedule, budget and staffing, see above, ref SDS 66 4745, and
391115 - Bootstrap strategy that proposes particular tasks to be
391116 - performed. ref SDS 0 9622
391117 - ..
391118 - Team decided today to focus project on OHS, which
391119 - initially entails adding addressability to email, ref SDS 0
391120 - 2760, and defer consideration of DKR, per below. ref SDS 0 6271
391122 - ..
391123 - CDS requirements prepared by Eric adopted as OHS requirements,
391124 - per below. ref SDS 0 2808
391126 - ..
391127 - No discussion of "storyboard" identifying multiple views to
391128 - improve software programming, per below. ref SDS 0 7238
391130 - ..
391131 - Progress today on email enhancements, per below, ref SDS 0 2760
391132 - continue work on use cases, ref SDS 0 4933, and begin pilot
391133 - test Wiki for prototype DKR to improve collaboration.
391134 - ref SDS 0 9000
391135 - ..
391136 - No schedule yet to develop architecture called out by
391137 - Jack Park on 000426, ref SDS 35 0304, review of design
391138 - requirements proposed by Eric Armstrong, per action item on
391139 - 000505, ref SDS 59 4864, and called out by Marcello on 000601
391140 - for attracting sponsor support. ref SDS 60 4080
391141 - ..
391142 - No progress reviewing starter technologies, per action
391143 - items proposed on 000601, ref SDS 60 3855, from meeting on
391144 - 000525, see below, ref SDS 0 4084, except, major step forward
391145 - on using Wiki for enhancing email collaboration, per below.
391146 - ref SDS 0 9000
391148 - ..
391149 - 2. Finding an organization that will take over operational
391150 - support.
391152 - ..
391153 - No progress reported on this vector.
391156 - ..
391157 - 3. Building the DKRs. ref SDS 60 2200
391159 - Per decision to concentrate on OHS, ref SDS 0 6271, no progress
391160 - on Jack Parks recommendation on 000426 to explain scope and
391161 - purpose of a DKR, ref SDS 35 2340, based on record of meeting
391162 - on 000518 explaining "knowledge," ref SDS 53 3528, and Marcello
391163 - Hoffman's suggestion on 000601 to identify a "hook" to attract
391164 - funding sponsors. ref SDS 60 4080
391165 - ..
391166 - Major step forward to pilot test Wiki for prototype DKR
391167 - to enhance email collaboration, per below. ref SDS 0 9000
391169 - ..
391170 - 4. Fellows program. ref SDS 60 5644
391172 - No discussion on this vector today.
Hoffman, Marcello, Lincoln, Pat
Funding Trip to Washington, Need Support for Open Source
Finance Requires Proof of Ability to Perform, 000601
Funding Requires Proof of Concept, 000601
High Tech Tourism, Fear Blocks Funding, 000601
SDS Proof of Concept DKR Knowledge Space, Jack Park, 000426
SPC Software Productivity Consortium
DARPA; DOD; Sun Microsystems; Mozilla; Gnutella
Mozilla Collaboration with OHS/DKR Development Opportunity
601401 - ..
601402 - Sponsors Looking for Projects in Knowledge Management
601404 - Follow up ref SDS 66 4877, ref SDS 60 4877.
601406 - Doug Engelbart and Pat Lincoln did not attend the meeting today, as a
601407 - result of being in Washington or other locals presenting the DKR story
601408 - to gain sponsor support.
601411 - ..
601412 - Mozilla Enthused About OHS
601413 - Gnutella Presentation Can be Scheduled
601415 - Follow up ref SDS 66 4868, ref SDS 60 4868.
601417 - Eugene reports that Mozilla enthused about OHS project, one of
601418 - their main engineers spent last few weeks reading Doug's papers on
601419 - his own time. Collaboration potential is very good .
601421 - [On 001101 Mozilla example open source projects have
601422 - overwhelming desire to use poor management. ref SDS 85 4O5K
601424 - ..
601425 - A Gnutella presentation can be scheduled for one of our meetings.
601426 - ref DRP 13 8610
601429 - ..
601430 - Doug/Pat Presentations for DARPA Next Week on Using Internet
601431 - SPC Workshop for DARPA on Applying Internet; Doug/Pat to Present
601433 - Follow up ref SDS 66 1760, ref SDS 60 1760.
601435 - Doug and Pat presenting this week at workshop in Washington D.C.
601436 - for DARPA.
601438 - ..
601439 - No discussion on notifying DARPA about ability to use the Net for
601440 - Knowledge Management that adds "intelligence" to daily meetings,
601441 - calls and other tasks, that supports Enterprise Management model,
601442 - commonly called a virtual or paperless office, submitted to the
601443 - project team in a letter, ref DIP 3 0001, on 000606, ref SDS 65
601444 - 0001, applying ideas presented to the team on 000518. ref SDS 53
601445 - 3528
601448 - ..
601449 - DOD Contacted Doug on DKR Opportunities
601451 - Follow up ref SDS 66 9702.
601453 - No report on follow up about email Doug received from the Senior
601454 - Advisor to the Secretary of Defense who is interested in scaling up
601455 - the Department of Defense's improvement infrastructure. ref DRP 12
601456 - 1360
601459 - ..
601460 - Sun Needs OHS Long Term, Wants Better Hardware Design Tools
601462 - Follow up ref SDS 66 0752.
601464 - No report submitted on results of meeting Doug and Pat had with Sun
601465 - to discuss how OHS can help solve problem of hardware design
601466 - software. Report on 000608 indicated Sun needs is better
601467 - interaction between software and hardware design tools; and in the
601468 - long term, Sun can use the OHS.
601470 - ..
601471 - How does the OHS need to be shaped to support Sun's objectives?
601474 - ..
601475 - Demo Project Deliverable Aids Sponsor Outreach
601476 - Funding Requires Initial Project Development
601478 - Follow up ref SDS 66 6821, ref SDS 60 6821.
601480 - Below, progress on Augment demo, and proposed video to attract
601481 - sponsor interest. ref SDS 0 9626
601483 - ..
601484 - Below, Wiki pilot test of prototype DKR provides beginning of mock
601485 - to demo project deliverables. ref SDS 0 3729
601488 - ..
601489 - Funding Requires Proof of Concept, Not High Tech "Tourism"
601491 - Follow up ref SDS 66 1007, ref SDS 60 1007.
601493 - No discussion today on developing prototype capability for
601494 - demonstrating better software programming by providing multiple
601495 - views, and email with addressability, per above, ref SDS 66 6821,
601496 - recognizes Marcello's recommendation on 000601 that getting funded
601497 - requires demonstrating useful tools rather than high-tech tourism.
601498 - ref SDS 60 1007
601500 - ..
601501 - No discussion today on implementing Knowledge Management based on
601502 - report by professor Mary Keeler at the meeting on 000518, showing a
601503 - development path to transition from documents to Knowledge Space,
601504 - ref SDS 53 2808, cited by Jack Park on 000426 that SDS provides
601505 - proof of concept for aspects of a DKR.
601506 - ..
601507 - Pilot test of Wiki DKR provides beginning of prototype to
601508 - demo project deliverables. ref SDS 0 3729
Summary Project for Funding Presentation
Summary Project Support Government Funding, Pat, 000601
Government Agencies, Funding Outreach
681001 - ..
681002 - Summarize Project Support Funding Inquiries for DKR
681004 - Follow up ref SDS 66 0852, ref SDS 60 0852.
681006 - No submission by Pat Lincoln on project summaries prepared from
681007 - member input for attracting sponsor funding, as planned during
681008 - meeting at SRI on 000608. ref SDS 66 8528
681010 - ..
681011 - No correlation reported with KM developed on 000518, as engine of
681012 - DKR project. ref SDS 60 2808
681014 - ..
681015 - No report on "hook" formulated to attract sponsor funding, cited by
681016 - Marcello Hoffmann on 000601. ref SDS 60 4080
681018 - [On 000622 called Marcello on progress. ref SDS 72 6816
681021 - ..
681022 - Audience for Sponsor Funding is Government Agencies
681024 - Follow up ref SDS 66 4896, ref SDS 60 4896.
681026 - No discussion on tailoring project summary for funding to audience
681027 - of government agencies, per agreement at the meeting last week.
681028 - ref SDS 60 4896
Software Programming Program Initial Product, 000406
Software Programming Multiple Views, Doug, 000601
Comments Only; Code Only - No Comments, 000608
Functions Only; Call Trees; Object Hierarchies, 000608
Collapsible Blocks; Context Highlighting; Change Logs, 000608
Improved Context Highlighting for Software Programming, 000608
Storyboard Design Features, 000608
Prototype Requested Software Programming Features, 000608
Software Programming Multiple Views, Doug, 000601
IP Protection Built into Architecture, Journaling, Lee Iverson, 000608
Prototype Software Programming Multiple Views, Doug, 000608
921401 - ..
921402 - Multiple Views, Storyboard Features
921403 - Software Programming Multiple Views, Storyboard Features
921404 - Programmers Initial Target Community Supports Bootstrapping
921406 - Follow up ref SDS 66 7238, ref SDS 60 7238.
921408 - No report on progress with storyboard work begun on 000608, and Doug's
921409 - request for schedule on prototype. ref SDS 66 7238 and, ref SDS 66
921410 - 4810
921412 - ..
921413 - On 000608 team may have adopted priority to focus initially on email
921414 - to provide addressability. ref SDS 66 2760
921416 - ..
921417 - On 000614 Eric Armstrong submitted a letter to the project DKR team
921418 - reviewing limited progress on software development, ref SDS 69 5826,
921419 - and recommending primary focus on CDS (OHS), because programmers
921420 - resist changing their tools. ref SDS 69 1938
921421 - ..
921422 - No discussion of Bootstrap planning, above, ref SDS 0 9622,
921423 - for developing stronger software programming, reviewed on 000614.
921424 - ref SDS 69 1650
921426 - ..
921427 - Concensus noted today to focus on email system with addressability and
921428 - catagories, per above. ref SDS 0 3855
921430 - [On 000718 DKR team proposal made by SRI to NASA proposes
921431 - improving software first. ref SDS 76 6020
Objective OHS Development Vector, Doug, 000405
Procedures and Tools Transcoding, IBM's WBI, 000324
Schedule for OHS Development Vector, Doug, 000405
Email Hyperdocuments Integrate
Email Improves with Links, Doug Sets for Team, 000405
Email XML Seed Team Use What is Available, 000302
Backlink Management, 000608
A21301 - ..
A21302 - Backlink Management Developed by Doug's Colleague Pending Review
A21303 - Email Addressability Needed to Aid Project, Demonstrate Progress
A21305 - Follow up ref SDS 66 2760, ref SDS 60 2760.
A21307 - Progress today on enhancing email to supplement software tools as
A21308 - "hooks" for attracting project sponsors, set as priority objective on
A21309 - 000601. ref SDS 60 0852
A21311 - ..
A21312 - Hypermail, adding linkability and citability requested by Doug at the
A21313 - meeting on 000601, ref SDS 60 2760, is beginning to take shape pilot
A21314 - testing a prototype DKR using Wiki explained below. ref SDS 0 3729
A21316 - ..
A21317 - No progress reported on questions from 000608. ref SDS 66 5510
A21318 - ..
A21319 - On 000614 Eric Armstrong proposes concentraing on enhancing
A21320 - email with CDS system, and deferring work on software programming
A21321 - development. ref SDS 0 7238
A21323 - ..
A21324 - Eric submits OHS minimum elements, per below. ref SDS 0 5880
A21326 - ..
A21327 - Doug may report at next meeting on a possible visit with Conklin about
A21328 - backlink management, while in D.C. this week. ref SDS 66 4725
Development Separate Forum from Objectives and Needs to Solve World P
Email Separate Forum for Development from Discussion World Problems
Email Forum Develop OHS DKR
SourceForge Server, Email Development, Eugene, 000608
A80701 - ..
A80702 - Separate Mailing List on Development of OHS, Possibly SourceForge
A80704 - Follow up ref SDS 66 5985, ref SDS 51 4971.
A80706 - No progress reported on setting up a project page on SourceForge for
A80707 - email on development of OHS, per planning at meeting on 000608.
A80709 - ..
A80710 - Report by Lee Iverson today on progress setting up pilot test of Wiki
A80711 - for prototype DKR may be related in providing an environment for
A80712 - collaborating with links, that generates a project record. ref SDS 0
A80713 - 3729
Sun Microsystems Donated Server Space
Sponsor Outreach, Support, 000324
Web Site Server Vendor
AG0701 - ..
AG0702 - Server Space for DKR Donated by Sun Microsystems
AG0704 - Follow up ref SDS 66 5962, ref SDS 60 5962.
AG0706 - No report of progress using server donated by Sun, per Eric's letter
AG0707 - on 00042, ref SDS 29 0001
Property Rights in Knowledge Organization
Ownership Investment Risk
Development Investment Risk
Open Source Evaluation
SRI Not Convinced Open Source Best Strategy
Engelbart Convinced Open Source Best Strategy
Study Needed Demonstrate Open Source Best Strategy, 000601
Open Source Study Viability OHS/DKR, Engelbart, Doug, 000601
Management Cannot Make Assignments
Authority, Leadership, Project Management
Open Source Similar Empowerment, Not Authority, No Responsibility
Accountability Essential Needs Authority, Open Source, Empowerment, D
AX1601 - ..
AX1602 - Legal Issues Arising from Open Source and Sponsor Support
AX1604 - Follow up ref SDS 66 3055, ref SDS 60 3055.
AX1606 - There was no discussion on getting a license or other standing
AX1607 - required to operate, noted at the meeting on 000330, ref SDS 20 3995,
AX1608 - possibly reflecting SRI will provide organizational platform, reported
AX1609 - 000420, ref SDS 28 6630, and Lee Iverson assigned full-time by SRI
AX1610 - 000504. ref SDS 42 7743
AX1612 - ..
AX1613 - There was no discussion about licensing issues discussed on 000324,
AX1614 - ref SDS 18 3055, nor of submission on 000421, by Eric Armstrong of
AX1615 - license ideas ref SDS 29 3055, nor of Paul Fernhout's submission on
AX1616 - 000513 proposing new ideas on licensing. ref SDS 49 0001
AX1617 - ..
AX1618 - Eugene expects to submit summary of the licensing issues for
AX1619 - consideration in reaching agreement on open source license by 000706,
AX1620 - per planning on 000608. ref SDS 66 6150
AX1622 - No other discussion today.
AX1624 - [On 000802 team proposes license. ref SDS 78 0001
AX1626 - ..
AX1627 - Open Source Evidence Showing Viability of Development Strategy
AX1628 - Study Cost Benefits of Open Source
AX1629 - Management Assignments Difficult to Make under Open Source
AX1631 - Follow up ref SDS 66 1976, ref SDS 60 1976.
AX1633 - Eugene Kim reported today that he is preparing the study requested
AX1634 - by Doug Engelbart on 000601 to evaluate open source strategy for
AX1635 - OHS/DKR. ref SDS 60 1976
AX1637 - ..
AX1638 - Eugene seemed to indicate the Open Source study would be ready
AX1639 - within the next two weeks or so.
AX1641 - [On 000802 team proposes license. ref SDS 78 0001
Knowledge Define, Distinguish Data, Information
Lessons Learned, Case Studies Root Cause Analysis
Giving Up on Knowledge Management, 000615
OHS Uses CDS Requirements, 000615
DKR Difficult Architecture, Hard to Design, Not Understood
Dilemma Industry Doesn't Know How to Design KM
Knowledge Management Not Understood, Eric Armstrong
KM Design Not Understood Secret of SDS
Design KM Too Difficult Not Enough Knowledge, Eugene Kim at SRI
OHS/DKR Project Gave Up on KM
Giving Up Latent Demand Not Driven by Need People Disallusioned Disap
Knowledge Not Well Enough Understood to Develop Knowledge Management
BO1501 - ..
BO1502 - DKR Project Knowledge Management Objective, Beginning with OHS
BO1503 - OHS Same as CDS Requirements Prepared by Eric Armstrong
BO1505 - Follow up ref SDS 66 2808, ref SDS 60 2808.
BO1507 - Per above, current vector is to produce a distributed CDS, explained
BO1508 - by Eric Armstrong as a predicate to OHS, ref SDS 0 3855, based on his
BO1509 - excellent set of requirements analysed on 000505, ref SDS 43 0001, and
BO1510 - pending review by the project team, including recent updates, e.g., on
BO1511 - 000614. ref SDS 69 0782, per below. ref SDS 0 5880
BO1513 - ..
BO1514 - On 000614 Eric proposed concentrating on improving email and deferring
BO1515 - work on software improvement, per above. ref SDS 0 7238 He provided
BO1516 - OHS minimum elements, and Bootstrap OHS Framework, per below.
BO1517 - ref SDS 0 5880
BO1519 - ..
BO1520 - Today, Eugene advised that the team plans to dispense with "CDS," and
BO1521 - use the project description of "OHS," since it reflects the largest
BO1522 - body of work produced by the project, thanks to Eric. This provides
BO1523 - an OHS deliverable that can be cited to attract funding sponsors, by
BO1524 - demonstrating the ability to perform, discussed on 000601. ref SDS 60
BO1525 - 6036
BO1527 - [On 000711 SRI submits pre-proposal to NASA for 3 year project to
BO1528 - develop OHS. ref SDS 75 0001
BO1530 - ..
BO1531 - [On 000928 Eugene Kim asked contributors to begin production work
BO1532 - on OHS. ref SDS 79 1Y9I
BO1534 - ..
BO1535 - [On 010205 Eugene recalls having suggested today that Eric just
BO1536 - call his stuff "OHS requirements" anyway. ref SDS 89 TE5O
BO1538 - ..
BO1539 - What Are We Trying to Accomplish Knowledge Management Beyond Reach
BO1540 - Lesson Learned Not Enough Known about Knowledge and KM for DKR
BO1541 - Knowledge Management Not Well Enough Understood to Develop DKR
BO1543 - Eugene reported during the meeting today that a consensus has formed
BO1544 - among project contributors over the past few months that there is not
BO1545 - enough knowledge to develop Knowledge Management" technology for the
BO1546 - OHS/DKR project. Eugene cited Eric's letter to the team on 000503,
BO1547 - saying the meaning of knowledge is hard to understand for building
BO1548 - computer tools that improve information management with email.
BO1549 - ref SDS 40 5033 Eric made this point again during a meeting at Intel
BO1550 - on 000517. ref SDS 52 5092 The team has not been able to answer Debra
BO1551 - England's question about "what we are trying to accomplish" building
BO1552 - technology for Knowledge Management, in her letter on 000420.
BO1553 - ref SDS 28 2808
BO1555 - ..
BO1556 - Eugene characterized this as a "lesson learned" It reflects Doug
BO1557 - Engelbart's report on 000504 that NSF denied funding for a project
BO1558 - proposal that did not define "knowledge." ref SDS 42 5555 More
BO1559 - recently, on 000602 Bill Beardon reported the team does not understand
BO1560 - how to define DKR. ref SDS 63 6162 On 910418 Intel reported engineers
BO1561 - need to figure out key scenarios for programming software to make
BO1562 - computers productive for management. ref SDS 1 UT7F On 950710 Landauer
BO1563 - reported engineers don't know how to do this task. ref SDS 4 3375 On
BO1564 - 950927 Intel gave up trying to make computers productive for managers.
BO1565 - ref SDS 5 7732 On 951011 Morris confirmed that software engineers
BO1566 - don't know how to make computers productive for management.
BO1567 - ref SDS 6 1341
BO1569 - ..
BO1570 - Supports proposition that Knowledge Management is a "secret" developed
BO1571 - on 000106. ref SDS 11 5120 again on 000425. ref SDS 34 0480
BO1573 - [On 000622 project team moved forward on knowledge management by
BO1574 - adding catagories to Augment. ref SDS 73 6652
BO1576 - [On 000623 Jack Park submits ideas on DKR architecture.
BO1577 - ref SDS 74 5826
BO1579 - ..
BO1580 - [On 000718 project submits proposal for Knowledge Management to
BO1581 - NASA. ref SDS 76 4410
BO1583 - ..
BO1584 - [On 000928 Eugene Kim reports project deliverable for KM was not
BO1585 - well understood. ref SDS 79 X57F
BO1587 - ..
BO1588 - [On 001017 DKR team at SRI reports funded to be awarded for OHS
BO1589 - and vision for architecture is pending. ref SDS 82 9622
BO1591 - ..
BO1592 - [...Eric Armstrong reports code for OHS begun, and architecture
BO1593 - makes sense. ref SDS 81 0001
BO1595 - ..
BO1596 - [On 001018 Eric reports snag in architecture. ref SDS 83 GD6J
BO1598 - ..
BO1599 - [On 001025 OHS Launch Plan does not define DKR. ref SDS 84 C9WP
BO1601 - ..
BO1602 - [On 001116 Jack Park letter to OHS/DKR team meeting at SRI
BO1603 - reports SDS records on the Internet demonstrate amazing
BO1604 - ability to accomplish Knowledge Management that validates
BO1605 - claims in POIMS. ref SDS 86 953G
BO1607 - ..
BO1608 - [On 020718 Eric defines knowledge. ref SDS 93 YX9L
BO1610 - ..
BO1611 - [On 020608 Dave Snowden reports research at IBM showing KM has
BO1612 - failed; proposes new efforts for 3rd generation. ref SDS 92 QV5G
BO1614 - ..
BO1615 - [On 020608 knowledge define case study hard for people to
BO1616 - grasp, ref SDS 92 CC6J; philosophy grounding for "Knowledge
BO1617 - Management" reviewed 050115, ref SDS 95 SF5K, correlates with
BO1618 - cognitive science reviewed 960518, ref SDS 7 GS58, management
BO1619 - tasks considered 000307, ref SDS 17 767G, and physical science
BO1620 - locality principle power of knowledge predicts and controls the
BO1621 - future, reviewed on 040312, ref SDS 94 YH4G
BO1623 - ..
BO1624 - Earlier, at the project launch meeting on 000324, Lee Iversion
BO1625 - reported that other KM efforts have encountered similar challenges,
BO1626 - ref SDS 18 4877, reflecting analysis submitted to the Colloquium team
BO1627 - on 000120. ref SDS 13 2688
BO1629 - ..
BO1630 - Bootstrap strategy, discussed above by Eugene, ref SDS 0 9622, calls
BO1631 - for using project experience to learn about knowledge management. This
BO1632 - requires working with a connected environment, called out by Doug on
BO1633 - 000326, and more recently on 000601. ref SDS 60 2760 Pilot testing
BO1634 - Wiki for a prototype DKR that provides a connected environment began
BO1635 - to be available 6 days ago, on 000609, per report below. ref SDS 0
BO1636 - 9000 Even though 6 days was enough for God to create the earth and
BO1637 - the heavans, we should be generous and allow ourselves more time to
BO1638 - create the DKR.
BO1639 - ..
BO1640 - On 000614 Eric submitted a letter providing links to a new
BO1641 - version of the CDS (also OHS, per above), and, also, linked to the
BO1642 - Bootstrap priorities, which says the General Specific Priority is to
BO1643 - build a Dynamic Knowledge Repository by bootstrapping, i.e. using what
BO1644 - we can get at any point to get close to what we want. ref SDS 69 8954
BO1645 - ..
BO1646 - This requires initially defining what is wanted.
BO1647 - ..
BO1648 - Giving up on knowledge management is similar to Peter Drucker's
BO1649 - lament in his book "Management: Tasks, Responsibilities..." reviewed
BO1650 - on 931130, complaining that people are giving up on "communication"
BO1651 - because it is difficult to fix or improve. ref SDS 3 3851 The DKR
BO1652 - team seems to feel that Drucker's concern about "communication" can be
BO1653 - solved by improving "collaboration" with better email. Communication,
BO1654 - however, is inherently a process that generates "knowledge." Better
BO1655 - communication therefore requires better management of "knowledge,"
BO1656 - which thereon requires a knowledge management capability, the core of
BO1657 - a DKR. We cannot solve the dilemma of KM, that so boggles the mind,
BO1658 - merely by switching the name to email and "collaboration," especially
BO1659 - where, as here, the very requirements we aim to implement, expressly
BO1660 - state the problem we seek to avoid. ref SDS 43 0782
BO1662 - [On 000928 Eugene Kim confirms project deliverable for Knowledge
BO1663 - Management not well understood. ref SDS 79 X57F
BO1665 - ..
BO1666 - [On 010605 Eugene makes same point at another meeting. ref SDS 90
BO1667 - RU5O
BO1669 - ..
BO1670 - [On 010917 Eugene says there is no single solution to knowledge
BO1671 - integration problem; does not define "knowledge." ref SDS 91 QQWQ
BO1673 - ..
BO1674 - Knowledge Management Definition
BO1676 - Follow up ref SDS 66 5555, ref SDS 60 5555.
BO1678 - There was no discussion of new information received at the meeting
BO1679 - on 000518 showing that Knowledge Management provides a unique path
BO1680 - to develop a DKR using an experiential record to improve human
BO1681 - memory that justifies funding, and that Doug's seed team may be
BO1682 - uniquely qualified to perform the work, responding to Marcello's
BO1683 - explanation on 000601 urging that the team avoid "high-tech
BO1684 - tourism." ref SDS 60 1007
BO1686 - ..
BO1687 - There was no discussion of Eric Armstrong's explanation on 000423
BO1688 - that the purpose of the DKR is to augment human intelligence,
BO1689 - reviewed recently on 000517. ref SDS 52 0585
BO1690 - ..
BO1691 - Lee reports below getting Wiki set up on the bootstrap.org
BO1692 - website, ref SDS 0 3729, planned on 000518, ref SDS 53 3944, to
BO1693 - strengthen project experience with a connected environment,
BO1694 - recommended on 000505 to support development of project specs for
BO1695 - knowledge management, ref SDS 43 5072, per Bootstrap strategy set
BO1696 - by Doug on 000326, and reviewed by Eugene today, per above.
BO1697 - ref SDS 0 9622
BO1699 - [On 000606 submitted project summary ideas based on project
BO1700 - record. ref SDS 65 0001
BO1702 - ..
BO1703 - [On 000928 Eugene Kim confirms project deliverable for
BO1704 - Knowledge Management now well understood. ref SDS 79 X57F
OHS Open Hyperdocument System
OHS Editor XML, Requirements, Specs
Atomic Data Structures, 000423
Collaborative Document System Email Core Capability DKR, Eric, 000505
DKR Data Structures, 000423
BY1101 - ..
BY1102 - OHS Editor Based on XML Initial Project Deliverable
BY1103 - Collaborative Document System and OHS Supported by Editor
BY1104 - CDS Change to OHS; Requirements Need Review by Project Team
BY1106 - Follow up ref SDS 66 5880, ref SDS 60 5880.
BY1108 - Per above, Eugene proposes changing the name of CDS to OHS.
BY1109 - ref SDS 0 2808
BY1111 - ..
BY1112 - No record of project review for specs v0.6, ref DRP 6 0001, issued
BY1113 - on 000508, ref SDS 44 0782, reviewed in depth on 000505.
BY1114 - ref SDS 43 0782, and updated by Eric on 000605. ref SDS 64 0782
BY1116 - ..
BY1117 - On 000614 Eric submitted CDS v0.9, also, pending review, and
BY1118 - alignment with architecture. ref SDS 69 0782
BY1120 - [On 001015 Eugene reported Eric's OHS specs have been reviewed
BY1121 - and results will be submitted oa 001030. ref SDS 80 RI9J
BY1123 - [On 010205 Eugene recalls having suggested today that Eric just
BY1124 - call his stuff "OHS requirements" anyway. ref SDS 89 TE5O
BY1126 - ..
BY1127 - Review will identify initial development scope, and support
BY1128 - resolution of KM difficulties reported above. ref SDS 0 6271
BY1130 - Use cases discussed below do not address Requirements.
BY1131 - ref SDS 0 4933
BY1133 - ..
BY1134 - On 000614 Eric submits OHS minimum elements linked in Requirements
BY1135 - v0,9. ref SDS 69 5296 This work was not reviewed today; schedule
BY1136 - for review pending. May be critical based on decision to focus on
BY1137 - OHS vector, per above. ref SDS 0 2808
BY1139 - ..
BY1140 - Bootstrap Alliance Tech Template Project 0 OHS Framework
BY1142 - Eric also provided yesterday a Bootstrap Alliance Technology
BY1143 - Template Project, OHS Framework showing detailed requirements
BY1144 - developed from Doug Engelbart's work, also, referenced with OHS
BY1145 - minimum elements and v0.9 of CDS specs. This material needs to be
BY1146 - correlated and synthesized with appropriate references to finalize
BY1147 - requirements. ref SDS 69 4710
BY1150 - ..
BY1151 - Atomic Data Structures Derive from Fundamental Information Unit
BY1152 - Fundamental Information Unit Focuses DKR Design Effort
BY1154 - Follow up ref SDS 66 4004, ref SDS 60 4004.
BY1156 - No evident discussion today of Joe Williams comprehensive
BY1157 - presentation on 000420 of DKR and OHS framework. ref SDS 28 4004
BY1159 - ..
BY1160 - No discussion of atomic data structures submitted by Eric on
BY1161 - 000423. ref SDS 32 4977
BY1163 - ..
BY1164 - No discussion of Paul Fernhout's submission on 000524 about
BY1165 - Pointrel Data Repository based on Python. ref SDS 54 0783
BY1166 - ..
BY1167 - No discussion nor schedule to review data structures
BY1168 - submitted by Eric Armstrong with v0.8 of Requirements, on 000605.
BY1169 - ref SDS 64 6984
Use Case Method Define Requirement, 00000000
Software Programming Program, Use Case Analysis, 000406
Use Case Email Prototype, Eugene, 000608
Use Case Prototype Email Addressability, Eugene, 000608
C50701 - ..
C50702 - Mind Maps, Concept Graphs Facilitate Use Case Analysis
C50703 - Use Case Methods for Software Design and Email Addressability
C50705 - Follow up ref SDS 66 4933, ref SDS 60 4933.
C50707 - No discussion of Eugene Kim's comprehensive submission on 000504
C50708 - suggesting the scope of OHS, and detailing specific use cases that
C50709 - improve literacy, supported by Jack Park. ref SDS 41 0784
C50711 - ..
C50712 - Last week the team planned for the meeting this week to go through
C50713 - use cases and come up with targets for prototyping deliverables...
C50715 - Software multiple views, ref SDS 66 4933
C50716 - ..
C50717 - Email enhancement, per above. ref SDS 0 2760
C50719 - ..
C50720 - Today, Eugene noted that purpose of Use Cases is to describe from
C50721 - very high level black box point of view. ref DRP 13 1178
C50723 - [On 000623 report Eugene did a great job developing use
C50724 - cases during meeting on 000622; no indication of reliance
C50725 - on project record. ref SDS 74 5826
C50727 - ..
C50728 - What is the user's goal - design a system with that in mind.
C50729 - ref DRP 13 1798
C50731 - ..
C50732 - Eric recommended keeping a good separation between design tangents
C50733 - and goals. ref DRP 13 1584
C50734 - ..
C50735 - No evident discussion of correlating use case work with
C50736 - project requirements developed by Eric, reviewed on 000505,
C50737 - ref SDS 43 0001, updated on 000601, ref SDS 61 0782 and again
C50738 - on 000605, ref SDS 64 0782, per above? ref SDS 0 5880
C50739 - ..
C50740 - Eugene mentions Rationale methodology, we do not Rational
C50741 - Corporation champions the cyclic Waterfall model of development.
C50742 - UML. Cyclic development model: feedback. (sic), ref DRP 13 7209
C50744 - ..
C50745 - Gil points out the different ways of doing Use Cases, particularly
C50746 - "Essential Use Cases" - Constantine, Essential Modeling.
C50747 - ref DRP 13 1786
C50749 - ..
C50750 - There are development methodologies such as Catellisis (sp?). Do
C50751 - mindmap and concept map of Mind map, i.e. concept map domain, get
C50752 - to shared understanding, share with users, then use case diagrams.
C50753 - ref DRP 13 7210
C50755 - Gil's Knoware might be applied for this task, per above.
C50756 - ref SDS 0 6864
C50757 - ..
C50758 - Exist in Eric's links. ref DRP 13 2112
C50760 - ..
C50761 - Eugene goes over one a Use Case, says not to get down in methodology
C50762 - and formal stuff so just keep that at the back of the mind rather than
C50763 - have it XMI is a DTD for UML upfront. Lee: XMI dtd for UML available
C50764 - at Argo. ref DRP 13 2310
C50765 - ..
C50766 - Eugene requests use cases for the DKR; recommends relying on
C50767 - intuitive idea of knowledge, ref DRP 13 3498, per report above on
C50768 - need for work up on "Knowledge Management," ref SDS 0 6271, called
C50769 - out by Doug on 000307.
C50771 - Need an example of relying on intuitive idea of "knowledge"?
C50773 - Can people rely on project glossary for definition of
C50774 - "knowledge," ref DRP 9 1242, to supplement intuition, submitted
C50775 - on 000602. ref SDS 63 3132
C50777 - [On 000622 no examples given nor explanation of why project
C50778 - record cannot be used to develop use cases for KM.
C50779 - ref SDS 73 0051
C50781 - ..
C50782 - [On 000623 report Eugene did a great job developing use
C50783 - cases during meeting on 000622; no indication of reliance
C50784 - on project record. ref SDS 74 5826
C50785 - ..
C50786 - Can the team rely on the project record, for example on
C50787 - 000518? ref SDS 53 3528
C50789 - ..
C50790 - Can team rely on Doug's reference to Bellinger on 000307?
C50791 - ref SDS 17 4820
Glossary, Engelbart, Doug, 000518
C90401 - ..
C90402 - Glossary Establishes DKR Culture, Supports Architecture for KM
C90404 - Follow up ref SDS 66 5783, ref SDS 60 5783.
C90406 - The glossary provides a key mechanism for developing in a deliberate
C90407 - manner a common culture and shared vision of the project mission and
C90408 - deliverables, as discussed on 000518. ref SDS 53 2808
C90410 - ..
C90411 - Lee has put the glossary prepared by Bill Bearden and Joe Williams on
C90412 - the Wiki web site, per below. ref SDS 0 5295
C90414 - ..
C90415 - This supplements publication on Joe's web site reported last week.
C90418 - http://www.hypermultimedia.com/DKR/glossary.htm.
C90420 - ..
C90421 - Today, Lee suggested ground rules and procedures for editing the
C90422 - glossary, ref DRP 13 5270, following up Joe's request at the meeting
C90423 - on 000608 for comments and suggestions for additions. ref SDS 66 5783
C90425 - ..
C90426 - Primary Glossary Supported by Separate Page for Each Term/Phrase
C90428 - Lee suggested that Joe and Bill are the only team members
C90429 - authorized to change the primary definitions of terms and phrases.
C90431 - Each such definition can be linked to a separate page showing
C90432 - suggestions, analysis, comments and links to other sources that
C90433 - comprise the history on which the summary project definition is
C90434 - based.
C90436 - ..
C90437 - Any team member may request a change in the primary definition,
C90438 - and any such request should be supported by reference to relevant
C90439 - history. Joe and or Bill must timely present such requests to the
C90440 - project membership for consideration. Upon determination to
C90441 - change the definition, Joe or Bill will make the changes, based
C90442 - upon and citing duly authorized instruction.
C90443 - ..
C90444 - Without getting overly officious, need procedures for
C90445 - submitting request to change a definition; getting it before an
C90446 - appropriate review panel; getting comments and recommendations,
C90447 - getting approval, and getting the change entered.
C90450 - ..
C90451 - Lee suggests that whoever signs the glossary should be responsible.
C90453 - ..
C90454 - Bill Bearden is going through it right now. Break each item up into a
C90455 - separate page. Number of page is unique in entire Zwiki. ref DRP 13
C90456 - 3128
C90458 - ..
C90459 - Have name anchor in OHS, so can refer to glossary: so can do
C90460 - Glossary#OHS to take user there. ref DRP 13 7700
C90462 - ..
C90463 - This helps address questions in the letter to Lee on 000609 asking
C90464 - about engineering management. ref SDS 67 4588
C90466 - ..
C90467 - Need to use similar care with OHS requirements and other project
C90468 - knowledge resources, per below. ref SDS 0 3729
Augment, Doug Engelbart's System at SRI Beginning in 1960s
Augment Human Capabilities
Augment Presentation, Engelbart, Iverson, Williams, Yee, 000420
CG0801 - ..
CG0802 - Augment Project at SRI in 1960s Sets Design Objectives
CG0804 - Follow up ref SDS 66 5992, ref SDS 60 5992.
CG0806 - Background...
CG0808 - On 000601 Eric asked for a description of Augment data structures
CG0809 - to expedite requirements for email system, ref SDS 60 5992, set
CG0810 - above, as project top priority, ref SDS 66 2760, as a predicate or
CG0811 - concurrent with prototype software multiple views. ref SDS 66 7238
CG0813 - ..
CG0814 - Augment can expedite developing work product for funding, per
CG0815 - Marcello Hoffman's report on 000601, ref SDS 60 3824, and Doug's
CG0816 - call for a prototype to demonstrate project objectives. ref SDS 66
CG0817 - 7238
CG0818 - ..
CG0819 - Earlier on 000330 Marcello reported that his research shows
CG0820 - nobody has developed a Knowledge Management capability, and that
CG0821 - Doug has a strong solution in Augment, which gives the DKR team an
CG0822 - advantage. ref SDS 20 0713 and ref SDS 20 2075
CG0824 - ..
CG0825 - On 000426 Jack Park reported that Augment sets stage for DKR
CG0826 - project, SDS on the Internet provides proof of concept for some
CG0827 - aspects of a DKR. ref SDS 35 3315
CG0829 - ..
CG0830 - On 000608 Augment demonstrated. ref SDS 66 4180
CG0833 - ..
CG0834 - Video of Augment Will Demonstrate OHS/DKR Objectives
CG0835 - Augment Needs Review for Data Structures Incorporate into OHS
CG0837 - Demonstration on 000608 showed a broad range of powerful capabilities,
CG0838 - that need review for incorporation into OHS/DKR requirements.
CG0839 - ref SDS 66 4180,
CG0841 - Joe showed the photos he took of Doug doing the Augment demo last
CG0842 - week. He suggested today that, since the demonstration was too fast
CG0843 - to recognize scope and usefulness of features, the project should
CG0844 - prepare a current video demo tape of Augment. ref SDS 66 3740,
CG0846 - ..
CG0847 - Joe proposes a planned production, and applying the Augment tutor
CG0848 - files, user manuals, and that the "chordian" is made USB. ref DRP 13
CG0849 - 1210
CG0850 - ..
CG0851 - John suggests we get hold of the Augment manuals / tutorial
CG0852 - documents and study them, mine them for our requirements, ref DRP 13
CG0853 - 2484, per Eric's request for Augment Data structures on 000601.
CG0854 - ref SDS 60 0672
CG0856 - ..
CG0857 - Joe will sit down with Doug to determine which Augment capabilities to
CG0858 - present and how to present it in a new video/vignette to highlight
CG0859 - Augment capabilities. ref DRP 13 1800
CG0861 - ..
CG0862 - Joe will do the scripting and prompting on Augment video.
CG0864 - [On 000621 received minutes of meeting from Su-Ling Yee.
CG0865 - ref SDS 71 0001
CG0867 - ..
CG0868 - The video will help attract funding by demoing KM capability, per
CG0869 - above. ref SDS 0 6821
CG0870 - ..
CG0871 - Su-Ling will find out if and where the 1968 video of NLS is
CG0872 - online (possibly at Stanford), ref DRP 13 7326
CG0874 - ..
CG0875 - An existing video on Augment available through Bootstrap was discussed
CG0876 - during the meeting today.
CG0878 - ..
CG0879 - Eric will watch the video and write up evaluation on incorporating
CG0880 - Augment into OHS requirements, ref DRP 13 8774, pending review by
CG0881 - project, reported on 000505. ref SDS 43 4864
CG0883 - ..
CG0884 - There was no discussion on Augment data structures requested by Eric
CG0885 - on 000601. ref SDS 60 0672
CG0887 - ..
CG0888 - Eugene will organize a viewing of the NLS video at SRI, probably on a
CG0889 - weekend day. ref DRP 13 9240
CODIAK Intelligence Capabilities
Guide to Running Nics, 000427
CL0501 - ..
CL0502 - Guide to Running NICs Gathers Intelligence, Provides Feedback
CL0503 - Communication Manager Proposed to Compliment Tools for DKR
CL0505 - Follow up ref SDS 66 3995, ref SDS 60 3995.
CL0507 - Nothing has been submitted responding to the request on 000428 for
CL0508 - more information on the Guide to Running NICs, ref DRP 3 3000,
CL0509 - proposed at the meeting on 000427. ref SDS 37 2867
CL0510 - ..
CL0511 - No record of work product showing contradictions and prodding of
CL0512 - contributors to grow knowledge repository's capabilities as we use it,
CL0513 - also proposed on 000427. ref SDS 37 2867
CL0515 - ..
CL0516 - Eugene has done a lot with the help of Su-Ling Yee to formulate
CL0517 - effective procedures on a range of project management issues,
CL0518 - including meetings, per above. ref SDS 0 4455
CL0520 - ..
CL0521 - Lessons learned from this experience provide case study to support
CL0522 - development of OHS and DKR capabilities, per Bootstrap strategy
CL0523 - reviewed by Eugene, above. ref SDS 0 9622
WBI Transcoding Vector
WBI 3 Tier Server Architecture, 000427
DirectDom, JDOM Processors of XML DKR, 000427
WBI Vector Presentation, Engelbart, 000420
Source Development System (SDS) Transcoding, 000511
SDS Source Development System Transcoding, 000511
Hitchiker's Guide To The Galaxy, DKR Example, 000615
Other DKR Projects Trying to Create OHS
CY1201 - ..
CY1202 - Current Proposal for DKR Transcoding - Complex Process
CY1203 - Architecture - Three-Tier Server for WBI Implementation
CY1205 - Follow up ref SDS 66 4674, ref SDS 60 4674.
CY1208 - ..
CY1209 - Eugene and Rod Have DKR Systems
CY1210 - Hitchiker's Guide To The Galaxy Good Example DKR
CY1212 - Eric commented that Eugene Kim and Rod Welch have prototype DKR
CY1213 - systems, reflecting the record on 000504, ref SDS 41 0001, and
CY1214 - previously by Adam Cheyer on 000406. ref SDS 22 6923 On 000407 a
CY1215 - letter to Adam with copy to Eugene and Doug Engelbart submitted a
CY1216 - government report showing KM saves time and money. ref SDS 23 0786
CY1218 - [On 001121 Rod notified the team SDS is available to learn how
CY1219 - to develop OHS capabilty by doing KM. ref SDS 87 XU8I
CY1221 - ..
CY1222 - [On 010131 Eugene submitted notice of availability to use his
CY1223 - tools for KM. ref SDS 88 XZ8G
CY1225 - ..
CY1226 - Lee Iverson suggested today looking at The Hitchiker's Guide To The
CY1227 - Galaxy site...
CY1230 - http://www.h2g2.com
CY1233 - ..
CY1234 - Lee says it's a DKR not an OHS, yet another open directory project,
CY1235 - a huge unfocused mindlessly open DKR. A good example of a DKR
CY1236 - that's not an OHS. ref DRP 13 1880
CY1239 - ..
CY1240 - Fundamental Issues of DKR Project Focused by DOM
CY1241 - DOM (Document Object Model) Uses XML for Doc Management
CY1243 - Follow up ref SDS 66 3640, ref SDS 60 3640.
CY1245 - No discussion on DOM and DDOM issue; nor, of W3C being ineffective
CY1246 - for data base; Python and Java supporting DOM for data base,
CY1247 - reported on 000504. ref SDS 42 3994
CY1250 - ..
CY1251 - Augment Data can be Transcoded
CY1253 - Follow up ref SDS 66 4558, ref SDS 60 4558.
CY1255 - Transcoding may have been shown in demonstration of Augment on
CY1256 - 000608, ref SDS 66 4180
Technology Review, Lee, 000525
Starter Technologies Using Develops Experience to Create KM
D00501 - ..
D00502 - Evaluate Starter Technologies, Volunteers
D00504 - Follow up ref SDS 66 4084, ref SDS 60 4084.
D00506 - Except for Wiki discussed below, ref SDS 0 9000, no other
D00507 - discussion of evaluations for starter technologies from action
D00508 - action item set by Lee Iverson at meeting on 000525. ref SDS 55
D00509 - 4084
ZWiki-style Collaborative Document System, 000427
Existing Capability, Start with What is Available, 000302
Pilot Test New Capabilities, 000227
Pilot Test Email for Organizing and Thought Tracking, 000428
DKR Starter Technologies, Email, Begin Using a System, 000504
Zwiki Lacks Time Stamp, no Accountability, Lee Iverson
Zwiki Permits Editing Other People's Original Work, Accountability Un
Accountability Missing Wiki Requires Social Contract, Lee Iverson
Wiki Difficult Implement Needs Social Contract, Lee Iverson
DL1201 - ..
DL1202 - Pilot Test Wiki for DKR Collaboration
DL1203 - Starter Technology Pilot Testing Wiki for Better Collaboration
DL1204 - Wiki Addressable Email Enhances Project Collaboration
DL1206 - Follow up ref SDS 67 0001, ref SDS 42 9000.
DL1208 - Lee confirmed his letter on 000609, ref DRP 11 0001, that Wiki
DL1209 - (also Zwiki??) is set up to enhance project collaboration per
DL1210 - priority to enhance email, explained above. ref SDS 0 2760
DL1212 - ..
DL1213 - He decided to go with WIKI on the Bootstrap site, rather than Zope,
DL1214 - ref DRP 13 5644, as planned on 000504. ref SDS 42 3944
DL1216 - ..
DL1217 - Difficulties with Zope were reported on 000525. ref SDS 55 3944
DL1218 - ..
DL1219 - Every Wiki page has it's own ID. Everything is in one
DL1220 - directory of pages. ref DRP 13 0800 There is no time stamp on
DL1221 - anything, so the team needs to follow ground rules in using this
DL1222 - resource to improve project work product. per below. ref SDS 0 3751
DL1224 - ..
DL1225 - Lee's letter on 000609, ref DRP 11 0001, provides an address to
DL1226 - access this new knowledge resource, ref SDS 67 0001, to support DKR
DL1227 - project work...
DL1230 - http://bootstrap.org:8080/OHS
DL1233 - ...and offers ground rules for using the resource...
DL1236 - ..
DL1237 - http://bootstrap.org:8080/OHS/GroundRules
DL1239 - ..
DL1240 - User can put up pure text; WIKI will format it using html.
DL1241 - ..
DL1242 - Lee's letter on 000609 explains the following resources are
DL1243 - on the site...
DL1245 - Ground Rules for accountability, per below. ref SDS 0 3751
DL1247 - http://bootstrap.org:8080/OHS/GroundRules)
DL1250 - ..
DL1251 - OHS (CDS) Requirements v0.8, received from Eric Armstrong on
DL1252 - 000605. ref SDS 64 5820
DL1254 - http://bootstrap.org:8080/OHS/Requirements
DL1256 - ..
DL1257 - Data structures submitted on 000605 are not yet incorporated,
DL1258 - ref SDS 64 6984, as shown on 000609. ref SDS 67 7476
DL1259 - ..
DL1260 - Glossary prepared by Joe Williams and Bill Bearden,
DL1261 - received initially from Bill on 000601. ref SDS 62 0001
DL1263 - http://bootstrap.org:8080/OHS/Glossary
DL1265 - ..
DL1266 - Use Cases prepared by Eugene Kim, received on 000516.
DL1267 - ref SDS 51 4393
DL1269 - http://bootstrap.org:8080/OHS/UseCases
DL1271 - ..
DL1272 - Links has 3 items from among many discussed by the project...
DL1274 - http://bootstrap.org:8080/OHS/Links
DL1275 - ..
DL1276 - Part of Sun's XML tutorial. Includes a discussion of
DL1277 - when to use attributes and when to use elements...
DL1279 - http://java.sun.com/xml/docs/tutorial/overview/4_design.html
DL1280 - ..
DL1281 - Human/Computer Interface. Describes a view of history
DL1282 - regarding the future of the interface
DL1284 - http://www.fourmilab.ch/autofile/www/chapter2_69.html
DL1286 - ..
DL1287 - Doug's famous NLS demo at the 1968 Fall Joint Computer
DL1288 - Conference.
DL1290 - http://sloan.stanford.edu/mousesite/1968Demo.html
DL1292 - ..
DL1293 - Help Desk
DL1295 - http://bootstrap.org:8080/OHS/HelpDesk
DL1298 - ..
DL1299 - Wiki has an infinite undo facility. ref DRP 13 4216
DL1301 - ..
DL1302 - Lee is the manager of the site. ref DRP 13 4550
DL1304 - Wiki home page should state Lee is manager and provide link to
DL1305 - "governance", with an explanation of duties, responsibilities
DL1306 - and authority, with a link to an authorization letter issued by
DL1307 - Doug, or a project management element.
DL1309 - ..
DL1310 - A login mechanism can be set up, but has not been set up as yet.
DL1311 - ref DRP 13 9894
DL1315 - ..
DL1316 - Accountability - Requires Social Contract
DL1317 - Members Setup Homepage for Comments, Nobody Changes Anything
DL1319 - Lee explained that the Wiki web site can be restricted so there's a
DL1320 - users list, but no restrictions are currently in place. The web
DL1321 - site is on a separate port that cannot be found except by people on
DL1322 - the DKR project list on eGroups. ref DRP 13 5593
DL1324 - ..
DL1325 - As set out in Lee's letter on 000609, he emphasized again today
DL1326 - that anybody can edit these Webpages. ref SDS 67 5825 and
DL1327 - ref DRP 13 5664
DL1329 - ..
DL1330 - Drawback is that WIKI has no time stamp. ref DRP 13 1575
DL1331 - ..
DL1332 - Team must use the site under a social contract to follow
DL1333 - ground rules, per above. ref SDS 0 5295
DL1335 - ..
DL1336 - Lee suggests that team members set up a homepage and use that as
DL1337 - the mechanism for commenting on primary DKR resources, such as the
DL1338 - glossary, the OHS requirements, etc.
DL1340 - ..
DL1341 - Each page is owned by somebody responsible for the content;
DL1342 - everyone can add comments, but not change original text. Can copy
DL1343 - an original to a version, will put suffix, and is linked to
DL1344 - original. WIKI is anarchical, any order is user enforced. Everyone
DL1345 - who wants to participate must look at the ground rules, suggest
DL1346 - changes if so inclined. ref DRP 13 1820
DL1348 - ..
DL1349 - Eugene encourages all to visit WIKI and look at the ground rules.
DL1350 - ref DRP 13 5510
DL1351 - ..
DL1352 - Glossary is discussed above. ref SDS 0 5783
DL1355 - ..
DL1356 - Prototype Email Enhancement for Collaboration
DL1357 - Collaboration, Prototype Enhance Email
DL1358 - Engineering Management Requires Procedures, Accountability
DL1360 - Rod asks questions previously submitted on 000609 concerning
DL1361 - engineering management, ref SDS 67 1008, shown in a letter to Lee
DL1362 - on avoiding mistakes, extra cost and delay. ref DIP 4 2294
DL1364 - [On 000727 Wiki DKR under review. ref SDS 77 9000
DL1366 - ..
DL1367 - Rod proposes that Eric should be the only one who makes changes to
DL1368 - the OHS/DKR requirements, ref DRP 13 2550, similar to Lee's
DL1369 - explanation on making changes to the glossary, per above.
DL1370 - ref SDS 0 6381
DL1371 - ..
DL1372 - Lee, Eugene and Eric emphasize that Wiki is just a tool for
DL1373 - us to experiment with right now, ref DRP 13 3953, per priority to
DL1374 - enhance email, explained above. ref SDS 0 2760
DL1376 - ..
DL1377 - It's not a model for what we want to do, simply a means to putting
DL1378 - everything together, organize thoughts and ideas, and keep a record
DL1379 - of that. ref DRP 13 5247
DL1381 - ..
DL1382 - It's just a tool for us to use right now, a convenience.
DL1383 - ref DRP 13 3584
DL1385 - ..
DL1386 - It's an online collaborative tool. ref DRP 13 3432
DL1388 - So is email. The aim is to improve email, per Doug on 000601.
DL1389 - ref SDS 60 2760 Email provides an audit trail, of sorts, which
DL1390 - needs to be incorporated into Wiki, per Lee's ideas on managing
DL1391 - the glossary, above. ref SDS 0 6381
DL1393 - ..
DL1394 - [On 000727 DKR team considering usng email because it seems
DL1395 - fast and easy. ref SDS 77 9000
DL1396 - ..
DL1397 - WIKI can serve as prototype for any kind of methodology,
DL1398 - ref DRP 13 1890, we can...
DL1400 - experiment with use cases. Nice to
DL1402 - expose anchors. Use purple numbers.
DL1404 - CSS style sheet exists.
DL1406 - Html gives a tweak, but xml is better.
DL1408 - Can define visualization style.
DL1410 - Infinitely cross-linkable.
Distribution. . . . See "CONTACTS"