Click here to comment!
1...Question -- Is knowledge simply a lot of information that is
2...Eugene's scope provides good "use case" material for building
CONTACTS
SUBJECTS
Time Information Integrate, Eugene Kim, 000504
DKR Projects Trying to Create OHS DKR, Competition
Sounds of Silence POIMS Things We Don't Talk About Around Here SDS Co
Observe SDS Demonstration Learn KM by Observing, Henry van Eykan, 001
Things We Don't Talk About Around Here SDS on Internet Demosntrates P
Study What Works Ponder SDS POIMS Com Metrics Things We Don't Talk Ab
4908 -
4908 - ..
4909 - Summary/Objective
4910 -
491001 - Follow up ref SDS 41 0000, ref SDS 39 0000.
491002 -
491003 - Eugene explains a DKR system he is developing. It has features that
491004 - can enhance the OHS/DKR project. Eugene's practice of taking a lot of
491005 - notes, ref SDS 0 6205, meets a threshold need for knowledge management
491006 - by providing information that can be converted into knowledge, which
491007 - can then be managed. He sets out an important idea of integrating
491008 - time and information. ref SDS 0 6033
491010 - ..
491011 - Sent ref DIT 1 0001 commending Eugene's DKR work, and asking for
491012 - examples of work product.
491014 - ..
491015 - Eugene responded that the system is under development, ref DRT 2 0001,
491016 - and indicates support for the SDS diary methodology. ref DRT 2 1352
491017 - Jack Park supports Eugene's scope for an Editor, and mentions Welch
491018 - methods may be hepful to the project. ref SDS 0 0625
491019 -
491020 - [On 000615 another DKR project cited. ref SDS 49 5972
491021 -
491022 -
491023 -
491025 - ..
4911 -
4912 -
4913 - Progress
491401 - ..
491402 - Use Case for OHS on Typical Knowledge Management Tasks Supports SDS
491403 -
491404 - Received ref DRT 1 0001 from Eugene Kim explaining use cases for the
491405 - DKR system he has created for his own work, which he mentioned at the
491406 - project launch meeting on 000324. ref SDS 20 2867
491407 -
491408 - [On 000505 Eric Armstrong submits updated version of specs for
491409 - editor that does not mention Eugene's work. ref SDS 43 0375
491411 - ..
491412 - [On 000516 Eugene submits use cases for software design.
491413 - ref SDS 45 4393
491415 - ..
491416 - [On 010131 Eugene makes his DKR tools available to the team for
491417 - open source development. ref SDS 57 XZ8G
491419 - ..
491420 - Eugene's 2nd letter explains tools for his DKR system are being
491421 - developed. ref DRT 2 0001 He comments favorably on SDS. ref DRT 2
491422 - 1352
491424 - ..
491425 - A letter from Jack Park, ref DRT 3 0001, supports Eugene's scope for
491426 - an editor to support a DKR. ref DRT 3 2115
491428 - ..
491429 - Jack describes cultural resistance to review POIMS, NWO, Communication
491430 - Metrics, as....
491431 -
491432 - things we don't talk about around here...
491433 -
491434 - ...must be pondered, because SDS enables a new way of working that
491435 - augments intelligence, as explained in POIMS, ref OF 1 3742, which is
491436 - demonstrated by the SDS record on the Internet. ref DRT 3 0288 Jack
491437 - made a similar point last week on 000426 noting that SDS is a proof of
491438 - concept for OHS/DKR. ref SDS 34 3315 An example is General Hank Hatch
491439 - now at Fluor Daniel who read NWO three (3) times in order to study how
491440 - SDS works, reported on 960403. ref SDS 6 5592
491442 - ..
491443 - Silence on SDS reflects Jack's letter on 000405 asking the OHS/DKR
491444 - team at SRI to discuss support for time and context using a diary and
491445 - journal model. ref SDS 23 2928 At and since that time, there has been
491446 - minimal response, with only Bill Bearden saying SDS is on the right
491447 - track. ref SDS 23 3877
491448 -
491449 - [On 000907 Jack presents research showing time, chronlology,
491450 - sequence applied with diary and journal methods help people track
491451 - "trains of thought," ref SDS 54 J69I; Jack cites Welch SDS
491452 - records on Internet for applying this method. ref SDS 54 E37M
491454 - ..
491455 - [On 000922 Jack baffled about why people have not addressed SDS
491456 - foundational documents, POIMS, NWO, Typical Day Scenario, even if
491457 - they do not try SDS, ref SDS 52 016R; he feels peer pressure may
491458 - be a factor; people feel funny "going first" to cite authority
491459 - for ideas for Knowledge Management that nobody else has
491460 - presented. ref SDS 52 FJ5H
491462 - ..
491463 - [On 001031 Jack noted again in a letter to the group that slow
491464 - progress developing Knowledge Management occurs from ignoring SDS
491465 - work product generated for the project, which results in failing
491466 - to study what works. ref SDS 53 2T9H
491468 - ..
491469 - [On 001130 Jack reports SDS has the structure for KM and the
491470 - right user interface for making KM useful to people. ref SDS 56
491471 - H17O
491473 - ..
491474 - [On 010411 Jack commends SDS subject index support for "finding
491475 - every little thing."
491477 - ..
491478 - [On 020904 Jack reports SDS deserves exposure. ref SDS 65 7D9L
491480 - ..
491481 - [On 071220 Jack advises SDS subject indexing worthy of
491482 - review. ref SDS 69 M53N
491484 - ..
491485 - Reflects Jason Yuen's concern that attitude of management at San
491486 - Francisco International airport must change in order to empower people
491487 - to adopt good management practics for saving time and money with SDS
491488 - and Com Metrics. ref SDS 11 QU4F
491489 -
491490 - [On 000922 citing POIMS and SDS for guidance creating effective
491491 - Knowledge Management resisted by social, cultural fear of
491492 - dissaffection among colleagues. ref SDS 52 U23L
491494 - ..
491495 - [On 010411 Jack fails to ponder POIMS to discover the secret of
491496 - KM. ref SDS 58 624N
491498 - ..
491499 - [On 010617 Jack unwilling to ponder POIMS to discover how SDS
491500 - enables continual learning that adds intelligence to information
491501 - that generates knowledge. ref SDS 60 895G
491503 - ..
491504 - [On 011003 Jack reported no clues have been developed from two of
491505 - years research on the OHS/DKR project for accomplishing KM in the
491506 - manner demonstrated by the SDS record on the Internet.
491507 - ref SDS 61 O74L
491509 - ..
491510 - [On 011208 Jack unwilling to ponder POMIS to discover how SDS
491511 - improves alphabet technology in order to augment intelligence.
491512 - ref SDS 62 4Q5L
491514 - ..
491515 - [On 011208 Jack urges developer to avoid "chest thumping" in the
491516 - face of total silence on advancing a culture of knowledge.
491517 - ref SDS 62 T84Y
491519 - ..
491520 - [On 020610 John Maloney indicates people don't talk about SDS
491521 - because POIMS explains a design to integrate management science,
491522 - computer science and cognitive science; this is foreign, funny
491523 - and alien to the language people encounter for computer programs
491524 - and management methods. ref SDS 63 N16F
491526 - ..
491527 - [On 020726 Tom Munnecke submits information calling for people to
491528 - study what works in order to improve the work. ref SDS 64 E63H
491530 - ..
491531 - [On 020924 Jack notes SDS justifies exposure through discussion,
491532 - commentary, writing, and experimentation, and that the developer
491533 - should not promote SDS. ref SDS 65 7D9L
491535 - ..
491536 - [On 040221 Jack asks about Gary making a presentation at SRI on
491537 - using SDS at aerospace company. ref SDS 66 AB6O
491539 - ..
491540 - [On 040312 going first to recognize ideas and writings that are
491541 - outside group acceptance is a common social, cultural dilemma
491542 - of Knowledge Management that slows progress, in this case
491543 - advancing Knowledge Management, incuding the scientific
491544 - community; people feel more comfortable rubbishing and ignoring
491545 - better ideas than to incur disaffection of colleagues.
491546 - ref SDS 67 U86L
491548 - ..
491549 - [On 051113 NWO cites Tesla invented alternating electrical
491550 - current for public utilities was ignored and rubbished by
491551 - experts with faith in a fiction impenetrable by truth.
491552 - ref SDS 68 C58G
491554 - ..
491555 - Yesterday Eric Armstrong proposed not considering "knowledge" because
491556 - it is hard to grasp a material difference from traditional information
491557 - technology. ref SDS 41 5033 Jack commented on advantages of Knowledge
491558 - Space that is supported by SDS, ref SDS 41 6138, which demonstrate a
491559 - difference from work product created using IT. Today, Jack feels that
491560 - one way or the other this SDS advantage must be pondered in order to
491561 - make progress toward Doug's vision to create OHS/DKR.
491562 -
491563 - [On 000824 Eric Armstrong reports Doug Engelbart proposed an
491564 - architecture for OHS/DKR based on SDS design. ref SDS 51 PU5N
491566 - ..
491567 - [On 001031 Jack submitted a letter noting that technology to
491568 - augment intelligence is more difficult to design than expected,
491569 - and possibly further recognizing SDS accomplishes this objective.
491570 - ref SDS 53 0S8L
491572 - ..
491573 - Eugene provides specific examples of knowledge management tasks that
491574 - are aided by technology to improve productivity of daily working
491575 - information, described by Doug Engelbart in his paper explaining
491576 - Knowledge Management objectives, published in 1972, and recently
491577 - reviewed on 000327. ref SDS 21 3971 This addresses in part my letter
491578 - to Eric on 000423, ref DIP 4 0001, asking for examples of how the
491579 - atomic data structures he specifies support KM. ref SDS 31 1521 On
491580 - 000424 a second letter to Eric, ref DIP 5 0001, noted that "use case"
491581 - analysis has seemed remote and esoteric relative to daily KM tasks
491582 - people perform. ref SDS 32 4083 Eugene's letter today, begins to
491583 - address that issue.
491585 - ..
491586 - Eugene notices the DKR team has stated the objective to initially
491587 - produce a software programming program, ref DRT 1 2193, reported on
491588 - 000406, ref SDS 24 5078, and confirmed recently in Eric's letter on
491589 - 000424. ref SDS 32 5460
491591 - ..
491592 - Eugene's letter, ref DRT 1 6674, provides a narrative on using OHS and
491593 - DKR for...
491594 -
491595 -
491596 - research
491597 -
491598 -
491599 - ...and later plans to submit information on using the capability
491600 - for...
491602 - ..
491603 - software development
491604 -
491605 -
491606 - email, managing
491607 -
491609 - ..
491610 - Generally, Eugene's letter fits the model of enhancing a wide range of
491611 - knowledge work, based on Eric's explanation that the purpose of the
491612 - DKR project is to produce a tool which will...
491613 -
491614 -
491615 - Augment human intelligence
491616 -
491617 -
491618 - ...as shown in his letter, ref DRP 6 1120, received on 000423.
491619 - ref SDS 31 5096 Eric's detailed explanation in the same letter...
491620 -
491622 - ..
491623 - An interactive tool for discussion and deliberation that records
491624 - the decisions and their rationales in way that allows the
491625 - knowledge gained in the process to be applied to future projects.
491626 - ref DRP 6 0001
491627 -
491628 -
491629 - ...shows general purpose support for thinking, which aligns with POIMS
491630 - that explains how technology to enhance alphabet technology, which is
491631 - the core competency of civilization, improves all forms of knowledge
491632 - work. ref OF 1 3742 A list of knowledge work improved by augmenting
491633 - human intelligence is set out in POIMS. ref OF 1 2688
491635 - ..
491636 - Eugene's 2nd letter today supports diary methods for "intelligence"
491637 - tools. ref DRT 2 1352
491639 - ..
491640 - Jack Park's letter today seems to support POIMS, and cites Eric's
491641 - detailed use case scenarios as a foundation for an OHS. ref DRT 3 0288
491642 - and ref DRT 3 1680
491643 -
491645 - ..
491646 - DKR to Manage Information Developed Past Three (3) Years
491647 - Doug's Ideas and Eugene's Work Yield Synergy and New Vision of OHS
491648 - Vision for OHS, DKR Combines Eugene's Work with Doug's Ideas
491649 -
491650 - Eugene has been designing tools to help manage information for
491651 - about three years. He noticed parallels in concept with Doug's
491652 - more sophisticated work developed over the past 40 years. Some of
491653 - Doug's ideas helped Eugene better understand requirements, and
491654 - have shown how certain features can make information management
491655 - much more effective. Eugene's letter today sets out a vision for
491656 - how an Open Hyperdocument System (OHS) that combines Doug's ideas
491657 - with Eugene's work in progress, can improve Eugene's work as a
491658 - researcher. ref DRT 1 5544
491659 - ..
491660 - Eugene's 2nd letter explains he is developing tools to
491661 - implement the scope set out in his first letter. ref DRT 2 1352
491663 - ..
491664 - Eugene's 2nd letter supports SDS diary methods for developing
491665 - "intelligence." ref DRT 2 1352
491667 - ..
491668 - Jack Park's letter support's Doug's objective to investigate
491669 - WBI, ref DRT 3 1760, and cites Doug's goals to improve human
491670 - productivity for solving world problems. ref DRT 3 0594
491671 -
491672 -
491673 -
491674 -
491675 -
491676 -
491677 -
4917 -
SUBJECTS
Define - Knowledge
Knowledge Acquisition
Define Knowledge Chronology Causation Experience
Define Knowledge, Intelligence, Distinguish Data, Information
Define Knowledge Seed Team, 000419
Integrate Time People Process, Eugene, 000504
Schedule, Contacts, Information, Integrate, Eugene, 000504
Time Management, Scheduling, Eugene, 000504
Contacts, Eugene, 000504
Integrate Schedule, Contacts, Eugene, 000504
PIM Paradigm Expand to POIMS, Eugene, 000504
Kim SDS Diary Supports Intelligence, 000504
Park SDS Provides Critical Requirements for KM, 000504
7815 -
781601 - ..
781602 - Research Supported by OHS and DKR
781603 -
781605 - ..
781606 - Research Requires Storing and Managing Information and Knowledge
781607 - Knowledge Consists of Researcher's Summaries and Commentary
781608 -
781609 - Research depends on storing and managing information and
781610 - knowledge. Raw information mostly takes the form of primary
781611 - source documents and information on those documents: text and Word
781612 - documents, e-mail, bibliographic information, etc. "Knowledge" in
781613 - my work generally takes the form of summaries and my own personal
781614 - commentary. Most of my notes consist of summaries of articles,
781615 - books, and lectures, with plenty of my own annotation. ref DRT 1
781616 - 0002
781617 -
781618 - Information is original source material.
781620 - ..
781621 - Knowledge is comprised of research summaries and personal
781622 - commentary, also annotation with respect to information from
781623 - original source material
781625 - ..
781626 - This is the first explanation from the DKR team on defining
781627 - "knowledge," set as an action item on 000407. ref SDS 25 2805 On
781628 - 000419 Doug suggested that the SRI "Seed" team define knowledge.
781629 - ref SDS 26 4964
781630 -
781631 - [On 000505 suggest that project specs define knowledge for
781632 - alignment with architecture. ref SDS 43 2356
781634 - ..
781635 - [On 000510 Joe Williams submits definition of knowledge.
781636 - ref SDS 44 0004, and notes that Doug was denied support by NSF
781637 - because the proposal did not define knowledge.
781639 - ..
781640 - [On 000516 Jack Park submits definition of knowledge.
781641 - ref SDS 45 4723
781643 - ..
781644 - [On 000517 data, information and knowledge defined during
781645 - meeting at Intel with Eric Armstrong and Morris Jones.
781646 - ref SDS 46 5096
781648 - ..
781649 - [On 000518 Doug Engelbart calls for glossary of terms for DKR
781650 - project. ref SDS 47 3286
781652 - ..
781653 - [On 000615 Eric reported there is not enough known about
781654 - "knowledge" to support development of Knowledge Management.
781655 - ref SDS 49 6271
781657 - ..
781658 - Jack Park submits a letter today that explains...
781659 -
781660 - Information
781661 -
781662 - ...is emails, journal papers, books, movies, diagrams,
781663 - recorded spoken words, and so forth.
781665 - ..
781666 - Interpreted context Build Indexes Build
781667 -
781668 - Build indexes into all that raw stuff. Indexes that make
781669 - sense for all potential users, and that's the really hard
781670 - part. ref DRT 3 1218
781672 - ..
781673 - Question -- Is knowledge simply a lot of information that is
781674 - accessible with indexes?
781676 - ..
781677 - Does Eugene's explanation of "knowledge" as including personal
781678 - commentary and annotation mean "opinion" is part of knowledge
781679 - that should be resposited in the DKR, per Jack Park's question
781680 - on 000405 about the role of "opinion" in the DKR? ref SDS 23
781681 - 2928
781683 - ..
781684 - How does this explanation of knowledge correlate with
781685 - Bellinger's work reported on 000307? ref SDS 19 5999
781687 - ..
781688 - How does Eugene's explanation relate to the definition of
781689 - knowledge in POIMS? ref OF 1 0561
781690 -
781692 - ..
781693 - Eugene's 2nd letter supports SDS diary methods for
781694 - developing useful "intelligence." ref DRT 2 1352
781695 -
781696 - Jack Park's letter suggests pondering Welch method.
781697 - ref DRT 3 0288
781699 - ..
781700 - How does Eugene's view align with review on 000120 of
781701 - Colloquium efforts to understand DKR? ref SDS 15 5063
781703 - ..
781704 - How does the definition align with work on 960227?
781705 - ref SDS 5 0022
781707 - ..
781708 - How does the explanation relate to researching Jeremy
781709 - Campbell's book on AI, reported on 900303? ref SDS 1 3002
781710 -
781712 - ..
781713 - Integrate Schedule, Contacts, Extends PIM Paradigm to POIMS
781714 - PIM Paradigm Extended by Integrating Personal with Organizational
781715 - Schedule, Contacts, Information Integrated in Knowledge Space
781716 -
781717 - Eugene needs technology to support information for...
781718 -
781719 - • bibliography
781720 - • contacts
781721 - • scheduling
781723 - ..
781724 - He feels that many tools address these needs; however, Eugene
781725 - wants the OHS to do things with raw, structured data that none of
781726 - the existing systems support. ref DRT 1 6660
781727 -
781728 - [On 000505 Eric Armstrong lists "Project Management" as a
781729 - "use" supported by DKR editor, which may reach to encompass
781730 - Eugene's new way of thinking. ref SDS 43 4212
781731 -
781733 - ..
781734 - Whole New Way of Thinking - Automate, Integrate Time and Info
781735 - Integrate People with Time and Process, New Way of Thinking
781736 -
781737 - Eugene offers an example: "...if I'm viewing my calendar and
781738 - see that I have a meeting with Joe Schmoe on Tuesday, I should
781739 - be able to click on his name to view his contact information.
781740 - With back-links, I can also do the reverse: I can find out
781741 - every instance Joe Schmoe appears in my calendar. ref DRT 1
781742 - 8586
781744 - ..
781745 - POIMS technology explains SDS integrates people, process and time
781746 - as the fundamental elements of management. ref OF 1 5884
781748 - ..
781749 - On 000208 Eric Armstrong asked for ideas on the core capability of
781750 - knowledge management. ref SDS 17 8960 On 000212 Eric proposed an
781751 - innovation of moving beyond the paradigm of information contained
781752 - only in "documents." ref SDS 18 9790 Eugene's idea today for
781753 - integrating time and information might support Eric's approach.
781755 - ..
781756 - On 000424 Adam Cheyer recommended that the project team listen to
781757 - Doug, and implement his ideas. ref SDS 32 1590 Eugene's work
781758 - today seems to follow Adam's advice by offering a whole new way of
781759 - thinking, which Doug calls out in the Bootstrap mission statement,
781760 - per analysis on 000424, ref SDS 32 5033, citing prior work on
781761 - 991222. ref SDS 14 3696
781762 -
781763 - Eugene's 2nd letter supports SDS diary methods for
781764 - developing "intelligence." ref DRT 2 1352
781766 - ..
781767 - Jack Park's letter supports Eugene's DKR scope, and
781768 - cite's Welch work. ref DRT 3 2115
781769 -
781770 -
781771 -
781772 -
7818 -
SUBJECTS
Organic Subject Structure
Reporting Based on Subject Context
Search DKR Method
Freelance Writer Eugene Explains OHS/DKR Can Organize Information for
8506 -
850701 - ..
850702 - Reports Based on Subject Context
850703 -
850704 - One of the things that freelance writers need to know is which
850705 - publishers to approach about articles or books. With a
850706 - combination of bibliographic and contact information stored in
850707 - the OHS, I can look at a list of book publishers and, with one
850708 - click, see a list of all of the books that they have published
850709 - and that are currently stored in my database, possibly filtered
850710 - based on category or some other field. From this data, I may
850711 - see that a certain publisher has printed a number of books that
850712 - I admire, and with that publisher's contact information
850713 - immediately at my disposal, I can quickly send a proposal.
850714 - ref DRT 1 6693
850715 - ..
850716 - On 000324 Eugene explained his background in publishing,
850717 - writing articles for computer magazines. ref SDS 20 0868
850719 - ..
850720 - Eugene links references to people (i.e., contacts) in his
850721 - note taking record with related information in his DKR.
850722 -
850723 - [...see above for integrating contacts and schedule.
850724 - ref SDS 0 6033
850726 - ..
850727 - He can click on people's names and find out their contact
850728 - information, their publications (with links to the ones that he
850729 - has read and summarized), and every reference to that person in
850730 - other publications and lectures summarized in his system, with
850731 - more detailed information just a click away. ref DRT 1 1880
850732 - ..
850733 - The objective to assemble information based on subject
850734 - content aligns with Adam Cheyer's presentation on 000406 where
850735 - he seemed to specify the OHS and DKR would support many
850736 - reports. ref SDS 24 1292
850737 - ..
850738 - Subject reports are a big part of SDS, explained in the
850739 - record on 980824, ref SDS 2 1411, because chronology shows
850740 - patterns of cause and effect to support decisions and reveal
850741 - opportunities, that are otherwise hidden by the complexity,
850742 - volume and speed of daily information, as reported on 991010.
850743 - ref SDS 12 3066
850744 -
850745 - Eugene's 2nd letter supports SDS diary methods for
850746 - developing "intelligence." ref DRT 2 1352
850748 - ..
850749 - Jack Park's letter supports Eugene's DKR scope, and
850750 - cite's Welch work. ref DRT 3 2115
850751 -
850752 -
850753 -
850754 -
850755 -
8508 -
SUBJECTS
Version Control
Lessons Learned, Cass Studies Root Cause Analysis
History, Experience, Lessons Learned, Case Study
Purpose DKR
9106 -
910701 - ..
910702 - Purpose of DKR Lessons Learned, Case Study, Experience
910703 - Version Control Needed in OHS
910704 - Historical Record of Understanding Brings New New Insights
910705 -
910706 - Eugene recommends that OHS support versioning, similar to
910707 - manual planning systems that leave a physical record of changes
910708 - in a schedule, for example meetings. The historical record is
910709 - useful to observe patterns of activity for improving procedures
910710 - or focusing on problems and opportunities. Most electronic
910711 - scheduling systems do not support versioning, which is a real
910712 - loss. ref DRT 1 4712
910713 -
910714 - [On 010618 Jack Park submits code for Nexist that aims
910715 - to accomplishes OHS/DKR objectives. ref SDS 59 BP3K
910717 - ..
910718 - Eugene might like the SDS schedule that is archived each
910719 - day, showing the information he cites.
910721 - ..
910722 - Backing up everyday, also provides versioning of records
910723 - that are regularly changed to reflect alignment with
910724 - subsequent activity, reflecting the dynamics of human
910725 - thought.
910727 - ..
910728 - Eugene wants to retain original interpretation notes. Notes
910729 - taken 10 years ago reviewed in the relation to subsequent
910730 - experience reveals errors in understanding. This "knowledge"
910731 - helps in a number of ways. ref DRT 1 8216
910732 -
910733 - This is a much larger issue than versioning; it goes to
910734 - the essence of knowledge as experience, history, lessons
910735 - learned and case studies.
910737 - ..
910738 - SDS pretty much accomplishes this objective.
910739 -
910740 - Eugene's 2nd letter supports SDS diary methods for
910741 - developing "intelligence." ref DRT 2 1352
910742 -
910743 - Jack Park's letter supports Eugene's DKR scope, and
910744 - cite's Welch work. ref DRT 3 2115
910746 - ..
910747 - Knowledge of history provided by access to the record,
910748 - described by Eugene, helps grow new knowledge based on the
910749 - process of thinking through writing, which Eugene supports
910750 - below. ref SDS 0 6205 See POIMS. ref OF 1 3742
910752 - ..
910753 - On 950204 SDS provides a lot of "firepower" to capture and
910754 - access history that expedites reading and writing.
910755 - ref SDS 3 4995 Below, Eugene explains specific editing
910756 - tools that support this effort. ref SDS 0 6205
910757 -
910758 -
910759 -
910760 -
910761 -
9108 -
SUBJECTS
Extensible Code Users Customize to Suit Preference
9403 -
940401 - ..
940402 - Extensibility to Customize Procedures Aids Knowledge Work
940403 -
940404 - Eric indicates OHS needs to support hyperlinking and backlinking
940405 - that enables users to customize how features are applied to suit
940406 - personal preferences and perspectives. The ability to customize
940407 - the work environment permits experimenting to discover and arrange
940408 - efficient and productive work practices. ref DRT 1 4960
940409 -
940410 - On 000129 Eric explained "extensible" as providing user the
940411 - ability to customize menus and key assignments. ref SDS 16 2064
940413 - ..
940414 - Today, Eugene discusses extensibility and customizablity. Are
940415 - these the same thing or complimentary features.
940416 -
940417 - [On 000505 extensible is part of Eric's specs for CDS,
940418 - unchanged from 000306. ref SDS 43 T75N
940419 -
940420 -
940421 -
940422 -
940423 -
9405 -
SUBJECTS
Pattern Recognition Intelligence Analysis
Writing Improves Thinking Planning Analysis
Structured Writing Improves Knowledge Management
Summary, Outline
Review Comments Differentiated
Commentary Indented Sub-point
Highlights, Symbols
Opinion Decision Support Purpose of DKR
Decision Support Part of DKR, 000405
Organize Manage Information
Structured Notes, OHS, Eugene, 000504
Improving Improvement, Continual Learning
AL14 -
AL1501 - ..
AL1502 - Use Case for Editing Features
AL1503 - Structured Notes Supported by Technology to Capture the Record
AL1504 - Summary, Outline, Highlights, Structure Aspects of Intelligence
AL1505 -
AL1506 - Eugene takes a lot of notes that summarize books, articles, or
AL1507 - lectures, which are intermingled with his annotations. ref DRT 1
AL1508 - 3942
AL1509 -
AL1510 - On 000405 Jack Park asked the DKR team about the role of
AL1511 - "opinion" in the DKR, which seems similar to Eugene's system
AL1512 - of "intermingling annotations." ref SDS 23 2928
AL1514 - ..
AL1515 - Eugene has noticed in the process of designing his DKR system that
AL1516 - following structure in his notes could be supported by OHS
AL1517 - technology...
AL1518 -
AL1519 - • outlining that is flexible.
AL1520 - • summaries
AL1521 - • commentary as an indented subpoint
AL1522 - • differentiate review comments
AL1523 - • color highlights
AL1524 - • distinguishing symbols.
AL1525 -
AL1526 - ...add value to traditional information forms. ref DRT 1 8670
AL1528 - ..
AL1529 - Summaries are an "interpretation" or restatement in the reviewers
AL1530 - words. ref DRT 1 8216
AL1531 -
AL1532 - Eugene's scope provides good "use case" material for building
AL1533 - the Editor, per above, ref SDS 0 6205, that will generate
AL1534 - information for the DKR, per the letter to Eric Armstrong on
AL1535 - 000424. ref SDS 32 4083
AL1537 - ..
AL1538 - Jack Park's letter supports Eugene's DKR scope, and cite's
AL1539 - Welch work. ref DRT 3 2115
AL1540 -
AL1541 - [On 000505 Eric Armstrong submits editor spec v0.5 listing
AL1542 - some of the features Eugene wants. ref SDS 43 5822
AL1543 -
AL1544 - [On 000622 Eugene proposes catagorizing nodes and links to
AL1545 - support structured discussion using IBIS. ref SDS 50 8160
AL1546 -
AL1547 -
AL1549 - ..
AL1550 - KM Improvement Requires Using KM Capabilities
AL1551 - Improving Improvement Means Using KM Methods on DKR Project
AL1552 -
AL1553 - On 000330 asked Eugene to submit notes on the DKR project
AL1554 - meeting. ref SDS 22 7546 On 000407 asked Eugene for comments
AL1555 - on the record for the meeting on 000330. ref SDS 25 2150
AL1556 - These occasions would have provided good "use cases" showing
AL1557 - how Eugene's methods improve the work.
AL1559 - ..
AL1560 - Knowledge management dilemma is how to get people who can
AL1561 - perform knowledge management, as Eugene describes today, to
AL1562 - demonstrate the work, and use it to help improve the process,
AL1563 - within the meaning of Doug's "improving improvement" model,
AL1564 - set out in his paper in 1992, reviewed on 991222. ref SDS 14
AL1565 - 3961
AL1566 -
AL1567 - [On 001126 Eugene calls for DKR team to learn KM by doing
AL1568 - KM using existing IT tools, rather than SDS, but does not
AL1569 - demonstrate how to accomplish this. ref SDS 55 T63N
AL1570 -
AL1571 -
AL1572 -
AL1573 -
AL1574 -
AL1575 -
AL16 -
SUBJECTS
Scheduling, Eugene, 000504
Action Item Follow Up Linked to Schedule, Eugene, 000504
Follow Up Planning Analysis
Use Case Method Define Requirement, 000324
Schedule, Contacts, Information, Integrate
Action Items
Command & Control of the Record
AV09 -
AV1001 - ..
AV1002 - Schedule Linked to Follow Up Aligns Future with Past Commitments
AV1003 - Follow Up Metric of Understanding Communication
AV1004 - Turn Plans into Action with Follow up Tools
AV1005 -
AV1006 - Eugene uses a "followup" annotation that says to find out more
AV1007 - information about a certain point.
AV1008 -
AV1009 - He can obtain a list of all items to follow up, linked to his
AV1010 - calendar or to do list. ref DRT 1 4860
AV1011 -
AV1012 - This is an important part of Command and Control of the
AV1013 - record, explained in POIMS. ref OF 1 1113
AV1015 - ..
AV1016 - Follow up supports feedback which is a critical metric of
AV1017 - understanding communication that supports the "intelligence"
AV1018 - process for converting information into useful knowledge,
AV1019 - explained in POIMS. ref OF 1 1106
AV1020 - ..
AV1021 - Follow up is further explained in NWO..., ref OF 2 2247
AV1022 -
AV1023 -
AV1024 -
AV1025 -
AV11 -
SUBJECTS
Alignment Avoid Meaning Drift
Linking, Power Accountability
Addressability
Granular Addressability Link Sources Original Alignment, Eugene, 0005
Alignment Avoid Meaning Drift
Align Communications, Testing Metrics
Accountability Link to Original Sources
Incite Inspiration Bring Innovation
Linking Dynamic Time Subject Management SDS Innovation
Links Aided by SDS Remembering What to Link
Accountable Results Not Following Rules Reengineer Needs Authority, S
Accountability Caused by Writing Talking Gives Deniability Get Credit
Fear Accountability KM Dilemma
Dilemma Industry Doesn't Know How to Design KM
Knowledge Dilemma Fear Accountability Brought by Knowledge
BI17 -
BI1801 - ..
BI1802 - Addressability to Original Sources Gives Power, Accountability
BI1803 - Alignment Linking Avoids Meaning Drift, Bumbling, Conflict
BI1804 - Accountability Brings Credit When Alignment Avoids Meaning Drift
BI1805 - Meaning Drift, Bumbling Avoided by Alignment Original Sources
BI1806 -
BI1807 - Scholarship requires citing original sources, which is called out
BI1808 - in ISO management criteria, reviewed on 950721. ref SDS 4 1740
BI1810 - ..
BI1811 - OHS support for addressability gives power and accountability to
BI1812 - create and maintain links to original sources. This helps
BI1813 - academics avoid inadvertent plagiarism (i.e. forgetting to
BI1814 - footnote a point, etc.). ref DRT 1 0775
BI1815 -
BI1816 - Eugene's 2nd letter supports SDS diary methods for developing
BI1817 - "intelligence." ref DRT 2 1352
BI1819 - ..
BI1820 - Jack Park's letter supports Eugene's DKR scope, and cite's
BI1821 - Welch work. ref DRT 3 2115
BI1823 - ..
BI1824 - [On 000602 Eugene provides link to web site with source
BI1825 - material that is disconnected from context and orginal
BI1826 - sources. ref SDS 48 3536
BI1828 - ..
BI1829 - Granular addressability allows links to data points in separate
BI1830 - documents. This helps. footnoting. For example, if I click on a
BI1831 - "footnote" (however a footnote in a traditional paper-published
BI1832 - article is represented in this system), I can not only get a
BI1833 - reference, I can go to my notes from that reference and see the
BI1834 - exact data point for that footnote. ref DRT 1 1591
BI1836 - ..
BI1837 - Addressability also allows me to reference primary source
BI1838 - information that I have in electronic form. For example, I can
BI1839 - link to the exact paragraph in an e-mail message from which I
BI1840 - derived certain information. ref DRT 1 2200
BI1841 -
BI1843 - ..
BI1844 - Fear of Accountability Knowledge Management Dilemma
BI1845 -
BI1846 - Enthusiasm for accountability aligns with management training,
BI1847 - but conflicts with resistance and fear of this management
BI1848 - metric, reported on 980405. ref SDS 10 5065
BI1849 -
BI1850 - A reasonable objective for the DKR project is to demonstrate
BI1851 - that better tools, like an OHS, for generating effective
BI1852 - "intelligence" will bring credit for developing needed
BI1853 - knowledge on time to cash in or opportunity, or avoid a big
BI1854 - mistake.
BI1855 -
BI1856 -
BI1857 -
BI1858 -
BI1859 -
BI19 -