CONTACTS 

SUBJECTS
OHS Open Hyperdocument System
Dynamic Knowledge Repository (DKR)
DKR Specification
Editor Development, 000505
Specifications, DKR, OHS
Editor Development, 000508
Fernhout SDS Supports Specificatino Review for KM, 000516
Communication Manager Saves Time So Managers Have Time to Think
Communication Manager Aligns Team Metrics Proactive
Communication Metrics Avoid Bumbling Discover & Fixes Mistakes
Communication Manager Ensures Time is Invested in Metrics Using Tools
Fernhout Commends SDS Review OHS Editor Specs
Knowledge Worker Communication Manager
Culture Accepts Com Manager Role Depend on Getting Common Story to Bu

2116 -
2116 -    ..
2117 - Summary/Objective
2118 -
211801 - Follow up ref SDS 74 0000, ref SDS 70 0000.
211802 -
211804 -  ..
211805 - Communication Metrics Supported by SDS Found Helpful
211806 -
211807 - Received ref DRT 1 0001 from Paul Fernhout responding to the review of
211808 - Eric's editor specs v0.6, received on 000508, ref SDS 70 0782, which
211809 - were posted for the project team on 000515, ref SDS 74 0001, and
211810 - included review comments from the record on 000505, which included the
211811 - stuff in v0.6. ref SDS 68 0001
211813 -  ..
211814 - Paul does not offer suggestions for improving the editor spec, nor on
211815 - the process of getting the work done, which is, also, discussed in the
211816 - record on 000505. ref SDS 68 1890
211818 -  ..
211819 - Paul indicates support for Communication Metrics applied by SDS, and
211820 - the quality of the work setting out the record, which supports the
211821 - Communication Manager role that Doug proposed at the meeting on 000427
211822 - setting up for the SRI team. ref SDS 61 2867
211823 -
211824 -
211825 -
211826 -
211827 -
211828 -
211829 -
2119 -

SUBJECTS
Property Rights in Knowledge Organization
Commercial Viability
Ownership Investment Risk
Open Source Development Freeware
Time for DKR Limited, 000423
Participation Rights of Contributors
Agreement Developed Shared Meaning, Vision
Decisons on Differences in Design and PM
Business Venture Failed, 000510
Binary Forces Permeate Human Endeavors, Cause Stress, Conflict
Competition, Cooperation, Innate Conflict to Integrated Tools

3613 -
361401 -  ..
361402 - Business Model Leadership Appreciated for Solving Open Source Issue
361403 - Recognition of Leadership on Open Source Solution Appreciated
361404 -
361405 - Follow up ref SDS 73 0001, ref SDS 71 0784.
361406 -
361407 - Paul's letter reported above, ref DRT 1 6278, expresses appreciation
361408 - for the letter on Saturday, ref DIP 1 0001, commending Paul's
361409 - leadership and ideas for solving open source issue. ref SDS 73 0001
361410 -
361411 -
361412 -
361413 -
361414 -
3615 -

SUBJECTS
Procedures Meeting Notes
Development Separate Forum from Objectives and Needs to Solve World P
Development Separate Email Forum, 000516
Record of Project Meetings, 000516
Zwiki DKR OHS Email Starter Technology with Addressability, 000504
Starter Technologies Using Develops Experience to Create KM
Starter Technologies Using Develops Experience to Create KM
Zope DKR OHS Email Starter Technology with Addressability, 000504

4410 -
441101 -  ..
441102 - Communication Separate Development from Other Issues
441103 -
441104 - Eugene proposes in a letter today creating a separate email forum for
441105 - development. ref DRT 2 0001
441106 -
441107 - Eugene suggests the DKR team should also create a new mailing list
441108 - focused entirely on OHS development, so we can continue to use the
441109 - current email forum to discuss broader issues regarding
441110 - collaboratively augmenting human intelligence. ref DRT 2 4875
441111 -
441112 -     [On 000608 discussed during project meeting at SRI. ref SDS 82
441113 -     5985
441115 -  ..
441116 - Progress on Starter Technologies to Enhance Email, Start DKR
441117 -
441118 - Lee Iverson is making progress setting up Zope/Wiki server for the
441119 - project. ref DRT 2 2881  On 000504 Lee reported progress setting up
441120 - Zope, ref SDS 67 3944, and that Wiki would support collaboration.
441121 - ref SDS 67 9000  On 000505 project requirements review shows need for
441122 - team to gain experience with connected environment. ref SDS 68 2852
441123 - On 000511 there was no report of progress on these efforts.
441124 - ref SDS 72 5922  Today's report shows improvement.
441125 -
441126 -      [On 000518 Lee reports Zope up and running on Bootstrap system.
441127 -      ref SDS 76 3944
441129 -       ..
441130 -      [On 000525 Lee reports Zope difficult to use. ref SDS 77 3944
441132 -       ..
441133 -      [On 000609 Lee reports Wiki system up and running.
441135 -       ..
441136 -      [On 000609 Lee explains social contract procedures for using
441137 -      Wiki.
441138 -
441140 -  ..
441141 - Record of Meetings Planned for DKR, Including Archiving
441142 -
441143 - Eugene proposes sending minutes of the weekly meetings at SRI to the
441144 - list of extended contributors, and, also, archiving the record.
441145 - ref DRT 2 1239
441146 -
441147 -     Need clarification on what is meant by "archiving."
441149 -  ..
441150 - Eric is commended for preparing a helpful record on the past few
441151 - meetings. ref DRT 2 7560
441152 -
441153 -      On 000421 Eric submitted notes for the meeting on 000420.
441154 -      ref SDS 56 0001
441155 -      ..
441156 -      On 000428 Eric submitted notes for the meeting on 000427.
441157 -      ref SDS 62 0001
441159 -       ..
441160 -      On 000504 Eric submitted notes for the meeting that day.
441161 -      ref SDS 67 0001
441163 -       ..
441164 -      On 000508 Eric reported that preparing the notes helped him
441165 -      understand the meetings better. ref SDS 69 5938
441167 -  ..
441168 - Eugene advises that starting this week, the project team will prepare
441169 - meeting minutes more formally. ref DRT 2 7560  This seems like a good
441170 - way to implement Doug's call at the meeting on 000427 for a Guide to
441171 - Managing NICs. ref SDS 61 2867
441173 -  ..
441174 - This implements Eugene's ideas for project management on 000330,
441175 - ref SDS 52 1376, aimed at implementing Doug's instructions on 000326.
441176 - ref SDS 50 5972
441177 -
441178 -      [On 000518 Howard Liu took notes on a notebook computer during
441179 -      weekly meeting at SRI. ref SDS 76 8160
441181 -       ..
441182 -      [On 000526 received Howard's notes. ref SDS 78 0001
441184 -       ..
441185 -      [On 000530 sent letter to Howard referencing Eugene's ideas on
441186 -      formal meeting minutes.
441188 -       ..
441189 -      [On 000530 received agenda and notes from Lee Iverson, but there
441190 -      are no actual notes; sent letter requesting the record of the
441191 -      meeting, per Eugene's proposal today. ref SDS 80 3596
441193 -  ..
441194 - Eugene suggests netcasting the weekly meetings. ref DRT 2 1120
441195 -
441196 -    This would be a great idea to encourage stronger preparation for
441197 -    meetings.
441198 -
441199 -    [On 000608 team reviewed this initiative. ref SDS 82 5094
441200 -
441201 -
441202 -
441203 -
441204 -
441205 -
4413 -

SUBJECTS
Use Case Software Program, 000424
Use Case Analysis, 000406
Use Case Method Define Requirement, 000324
Use Cases for Software Development, 000516

4806 -
480701 -  ..
480702 - Software Development Use Case Issues
480703 -
480704 - Received ref DRT 3 0001 from Eugene Kim setting out elements of a
480705 - project for software development.
480706 -
480707 - This letter supplements Eugene's excellent narrative on 000504 of use
480708 - cases he would like for a knowledge management, ref SDS 66 0784,
480709 - including a definition of knowledge. ref SDS 66 5003
480711 -  ..
480712 - This seems to be a set of steps for creating anything, not simply
480713 - software programs, similar to Lee Iverson's letter on 000427, that
480714 - provided project management processes which can be used for software
480715 - development or any other kind of project, ref SDS 60 1462, and also
480716 - similar to the atomic data structures prepared by Eric Armstrong,
480717 - received on 000423. ref SDS 58 4933
480718 -
480720 -  ..
480721 - Eugene's submission today needs narrative on functionality, scenarios
480722 - and benefits, like his letter on 000504. ref DRP 1 0002
480724 -  ..
480725 - In particular Eugene says...
480726 -
480727 -    1.  Start a new project.
480728 -
480729 -        a.  Develop (Propose, Comment, Summarize, Finalize, Revise,
480730 -            Deprecate, Browse) goals.
480732 -              ..
480733 -             See similar scope and questions about Lee Iverson's
480734 -             submission on 000427. ref SDS 60 0004
480736 -             ..
480737 -        b.  Develop use cases.
480738 -        c.  Develop requirements.
480740 -              ..
480741 -             See similiar scope and questions on 000427. ref SDS 60
480742 -             6334
480744 -             ..
480745 -        d.  Develop design.
480746 -        e.  Develop documentation.
480748 -         ..
480749 -    2.  Link documents to other documents.
480750 -
480751 -        a.  Link goals to use cases.
480752 -        b.  Link use cases to requirements.
480753 -        c.  Link requirements to source code.
480754 -        d.  Link requirements to design.
480755 -        e.  Link documentation to use cases.
480757 -               ..
480758 -              [On 070126 case study people giving up on linking.
480759 -              ref SDS 86 YV4F
480761 -         ..
480762 -    3.  Integrate legacy data.
480763 -
480764 -        a.  Integrate legacy documents (documentation,
480765 -            e-mail/discussion, source code).
480767 -             ..
480768 -        b.  Link legacy documents.
480770 -         ..
480771 -    4.  Evaluate (Propose, Comment, Summarize, Finalize) software upon
480772 -        which system might be built.
480774 -         ..
480775 -    5.  Manage release.
480776 -
480777 -        a.  Assign tasks.
480778 -        b.  Manage (submit, comment, revise, incorporate) patches.
480779 -        c.  Link patches to documents.
480781 -         ..
480782 -    6.  Track bugs.
480783 -
480784 -        a.  Report a bug.
480785 -        b.  Assign a bug.
480786 -        c.  Link bugs to patches.
480788 -         ..
480789 -        Contribute source code.
480791 -         ..
480792 -        Volunteer for task.
480793 -
480795 -  ..
480796 - These "use case" objectives and requirements are supported by SDS, as
480797 - set out in the record on 000524 proposing Communication Metrics for
480798 - engineering support at Intel. ref SDS 7 0876
480800 -  ..
480801 - On 000525 Morris reported that engineers would not perform these steps
480802 - even if supported by technology. ref SDS 8 0966
480803 -
480804 -     [On 000517 meeting at Intel with Eric Armstrong and Morris, there
480805 -     was discussion that people at Fry's will not pay $20 for this
480806 -     capability. ref SDS 75 4275
480807 -
480808 -
480809 -
480810 -
4809 -

SUBJECTS
Knowledge Define Justified True Belief Support Technology Developmen

5703 -
570401 -  ..
570402 - Justified True Belief Knowledge Definition Objective DKR Technology
570403 - Knowledge Defined to Support DKR Project "Justified True Belief"
570404 -
570405 - Follow up ref SDS 71 0004, ref SDS 66 5003.
570406 -
570407 - Received ref DRT 4 0001 from Jack Park submitting a definition of
570408 - knowledge from the following website...
570409 -
570410 -              http://www.uta.fi/~attove/vehka-f.htm
570411 -
570412 - ...from: Extended concept of Knowledge for Evolutionary Epistemology
570413 - and for Bisemiotics, setting out this definition....
570414 -
570415 -      "The standard philosophical conception of knowledge defines
570416 -      knowledge as a true well-justified belief or proposition.
570417 -      Knowledge is achieved, at least in standard empiricist dogma, by
570418 -      some learning process, either through perception or through the
570419 -      adoption of such a tradition that contains previously gathered
570420 -      knowledge. In the tradition of EE followed here, an analogy
570421 -      between evolutionary adaptation through natural selection and the
570422 -      increase in environmental knowledge is emphasized. More
570423 -      specifically, this knowledge is not simply about the environment,
570424 -      but rather about the relationships between the knower (e.g.
570425 -      organism) and its environment."
570427 -  ..
570428 - This responds in part to the suggestion on 000503 for Jack to provide
570429 - guidance on defining "knowledge." ref SDS 64 1209
570431 -  ..
570432 - Seems to align with prior review of philosophy defining "knowledge,"
570433 - reported on 991027. ref SDS 10 SL9G
570434 -
570435 -            [On 050115 research on philosophy define knowledge
570436 -            justified true belief, ref SDS 85 SF5K; very interesting
570437 -            paper, but not sure this provides good grounding for a
570438 -            practice and tools for Knowledge Management, ref SDS 85
570439 -            845K; except Peirce explains knowledge requires continual
570440 -            refinement to obtain accuracy. ref SDS 74 7380
570442 -  ..
570443 - Curious that philosophy does not seem to define "knowledge" in terms
570444 - of correlating cause and effect, discussed in POIMS. ref OF 1 0367
570445 - Information can occur on x, and on y, but only becomes knowledge when
570446 - x and y are connected to yield predictability, i.e., causation, noted
570447 - previously on 991027, ref SDS 10 SL9G, and citing an example
570448 - distinguishing information from knowledge developed on 900303
570449 - reviewing Jeremy's Campbell's book on cognition. ref SDS 1 7739
570451 -  ..
570452 - Peirce, on the other hand, seems to recognize the weight of experience
570453 - as evidence in forming knowledge, indicated by Mary Keeler's paper
570454 - received from Jack yesterday. ref SDS 74 0042
570456 -  ..
570457 - Jack's letter today providing a defining knowledge, ref SDS 0 4723,
570458 - supplements Eugene's explanation of knowledge on 000504, ref SDS 66
570459 - 5003, and Joe Williams' submission on 000510. ref SDS 71 0004
570460 -
570461 -    [On 000517 "data," "information" and "knowledge" defined during
570462 -    meeting at Intel with Eric Armstrong and Morris Jones, ref SDS 75
570463 -    0785, citing prior meeting on 960227, ref SDS 5 0022, and POIMS.
570464 -    ref OF 1 0561
570466 -     ..
570467 -    [On 000518 Doug Engelbart called for glossary to define terms used
570468 -    by DKR project. ref SDS 76 3286
570470 -     ..
570471 -    [On 000601 Bill Bearden submitted first draft of glossary that
570472 -    defines knowledge. ref SDS 81 0001
570474 -     ..
570475 -    [On 000623 Jack proposes KM architecture, but does not tie to the
570476 -    definition submitted today on knowledge. ref SDS 83 4048
570478 -     ..
570479 -    [On 040312 power of knowledge to control the future derives from
570480 -    energy exchanged in connections of cause and effect, generally
570481 -    arising under the locality principle. ref SDS 84 YH4G
570482 -
570483 -
570484 -
570485 -
570486 -
570487 -
570488 -
570489 -
570490 -
5705 -