CONTACTS 
0201 - Bootstrap Institute                  510 713 3550
020101 - Mr. Douglas C. Engelbart, Ph.D.
020102 - doug@bootstrap.org
0202 - IBM Almaden Research Center          408 927 1898
020201 - Mr. Michael C. Wirth, Ph.D.; Manager USR Software =408 927 1898
020202 - wirth@almaden.ibm.com
020203 - User Systems Ergonomics Research

SUBJECTS
OHS/DKR Meeting at SRI 000420
Williams, Joe
OHS, 000307
DKR Specification
DKR, 000422
Williams, Joe

0908 -    ..
0909 - Summary/Objective
0910 -
091001 - Follow up ref SDS 69 0000, ref SDS 68 0000.
091002 -
091003 - Received ref DRT 1 0001 from Joe Williams which seems to supplement
091004 - the record on his presentation, ref SDS 68 5880, provided by Eric
091005 - Armstrong in a letter, ref DRP 1 0001, on 000421, ref SDS 69 0001,
091006 - setting out results of the meeting at SRI on 000420. ref SDS 68 0001
091007 -
091008 -     [On 000429 letter from Joe clarifies scope of DKR and OHS
091009 -     specification. ref SDS 72 0001
091010 -
091011 - Since the purpose of the letter is to clarify the presentation,
091012 - analysis is included in the record on 000420. ref SDS 68 4004
091013 -
091014 - Joe is adding the license paragraphs suggested by Eric, evidently from
091015 - Eric's letter on 000421. ref SDS 69 3055
091016 -
091017 -
0911 -

SUBJECTS
Use Case Method Define Requirement, 01020100
DKR Design, Joe Williams, 000429

1805 -
180501 -  ..
180502 - Use Case Analysis for DKR and OHS Design
180503 -
180504 - Follow up ref SDS 68 4933, ref SDS 46 6052.
180505 -
180506 - Received 2nd letter from Joe, ref DRT 2 0001, providing use case
180507 - analysis, based on Lee Iverson's presentation at the meeting on
180508 - 000420, ref SDS 68 4933, and evidently directed toward the "picture"
180509 - presentation Joe made at the same meeting on 000420. ref SDS 68 4004
180510 -
180511 -     [On 000429 letter from Joe clarifies scope of DKR and OHS
180512 -     specification. ref SDS 72 0001
180513 - ..
180514 - This is the best (and only) overall explanation by the SRI team,
180515 - or anyone else, of how a DKR might work, and what it is supposed to
180516 - do. On 000330 Marcello Hoffman noted that nobody has solved this
180517 - knowledge management dilemma. ref SDS 53 0713  On 000414 Eric
180518 - recommends Traction for a good DKR program to support email.
180519 - ref SDS 66 3450
180520 -
180521 -     [On 000423 Eric submits atomic data structures that seems to build
180522 -     on Joe's ideas. ref SDS 70 4933
180523 -
180524 - Need correlation and conflicts between Joe's use case study today, and
180525 - Eric's work on requirements for OHS/DKR, presented most recently on
180526 - 000406. ref SDS 59 0375,
180527 - ..
180528 - Use cases are not presented in sufficient detail to show the
180529 - level of effort entailed, what tools are needed, how they would be
180530 - used, how daily working arrangements might be changed or impacted, and
180531 - what benefits would be derived relative to present practice, as
180532 - related on 000120. ref SDS 23 2546
180533 -
180534 -
180535 -    1.  Name this DKR.
180536 -
180537 -        Establish the 'namespace' of this DKR. the first set of 8
180538 -        characters of this DKR name is provided by you, the DKR
180539 -        administrator. The second set of eight characters is supplied
180540 -        by bootstrap alliance. Together they form a string that
180541 -        uniquely identifies this DKR and allows interface with other
180542 -        DKR installations. ref DRT 2 1320
180543 -
180544 -        Questions...
180545 -               ..
180546 -           a.  Is 8 characters enough for either user or
180547 -               Bootstrap?
180548 -
180549 -               Probably, if they are alphanums.
180550 -
180551 -               Can there be spaces, as with winnows?
180552 -
180553 -           b.  Is this a generic capability people can use to set up
180554 -               their own DKR, and of so, is the first criteria the
180555 -               user and the second the organization or ISP?
180556 -
180557 -           c.  How does this compliment or improve current methods of
180558 -               defining web space?
180559 -
180560 -           d.  Is Bootstrap going into the ISP business?
180561 -
180562 -
180563 -    2.  Define the DKR GOAL.
180564 -
180565 -        Each DKR Goal, or Problem, is a separate information item.
180566 -
180567 -        Each entry describes the user's the purpose. ref DRT 2 2812
180568 -
180569 -        An example DKR goal is;
180570 -
180571 -                 "Eliminate World Hunger".
180572 -
180573 -        Another is:
180574 -
180575 -                 "Identify ways to improve the DKR/OHS interface".
180576 -
180577 -        You can choose the title for this group of entries, either
180578 -        Goal, or Problem, or whatever you feel will serve to focus the
180579 -        efforts of contributors as the purpose of this DKR,
180580 -
180581 -        Question
180582 -           ..
180583 -           What are "goals"?  Is it the same as objectives,
180584 -           class, catagories, hopes, etc.?
180585 -           ..
180586 -           Do we need guidance on how to address challenge of
180587 -           scale that arises from unlimited goals, e.g., from "world
180588 -           hunger" to "I want a cookie"?
180589 -           ..
180590 -           Does Jack Park's ontology requirement apply, from work
180591 -           on 000221? ref SDS 34 8044
180592 -        ..
180593 -    3.  Define the main content structures.
180594 -
180595 -        For this example, the categories are levels...
180596 -
180597 -                 1: Experience,
180598 -                 2: Learning, and
180599 -                 3: Knowledge.
180600 -
180601 -        While there can be any number of content structures, the
180602 -        abstract naming in this example assumes that information will
180603 -        progress thru these structures with progressively greater
180604 -        detail and refinement, from Experience to Learning, to
180605 -        Knowledge. ref DRT 2 5550
180606 -
180607 -          [On 000423 Eric sumbits "catatories", ref SDS 70 0780
180608 -
180609 -         ..
180610 -        Question and Comment....
180611 -
180612 -           Is the idea to provide levels of summary, which is very
180613 -           useful, see POIMS. ref OF 1 8316
180614 -
180615 -           On 000413 Traction provides summarizing and hierarchial
180616 -           features. ref SDS 65 5077
180617 -           ..
180618 -           Need example of how Experience, Learning and Knowledge
180619 -           levels are applied?
180620 -           ..
180621 -           How does use of learning and knowledge relate to
180622 -           Bellinger's approach, which Joe seemed to support on 000307,
180623 -           ref SDS 38 0651, and again at the project meeting on 000324.
180624 -           ref SDS 46 4140
180625 -
180626 -        For the general case, there can be any number of levels, any
180627 -        number of categories in each level, and any number of items in
180628 -        each category. ref DRT 2 1764
180629 -
180630 -        Question
180631 -           ..
180632 -           Need example of how multi-level catagories is
180633 -           accomplished.
180634 -
180635 -        Implict in the DKR definition is that content is somehow more
180636 -        focused on a goal as the level increases. In this example,
180637 -        Experience is the level at which real life facts and
180638 -        observations are gathered and entered into the repository.
180639 -        These individual data items are deliberated by the participants
180640 -        and organized into cohesive lessons then moved to Learning.
180641 -        Each Learning item proves or supports one Knowledge item, which
180642 -        is linked to a DKR Goal. ref DRT 2 1755
180643 -
180644 -        Question....
180645 -           ..
180646 -           How does this relate to case studies and lessons
180647 -           learned?
180648 -           ..
180649 -           What does "move" mean and how is it accomplished?
180650 -           ..
180651 -           How does this relate to lessons learned in the human
180652 -           mind?
180653 -
180654 -    4.  Load the Knowledge category.
180655 -
180656 -        Enter a separate informaton item for each descrete fact known
180657 -        about the goal. These should be the few core 'facts' presently
180658 -        'known' about the goal. ref DRT 2 6545
180659 -
180660 -        Question...
180661 -           ..
180662 -           Need example illustrating...
180663 -
180664 -               information item
180665 -               discrete fact known
180666 -
180667 -                   What constitutes a "known" fact?
180668 -
180669 -                   How do we know when we "know" something?
180670 -
180671 -           Who does this "entry" and when does it occur?
180672 -
180673 -           Suppose the person is absent, is in a meeting, or on
180674 -           vacation, how do separate inforamtion items get entered, and
180675 -           if they don't how does that impact the DKR?  How does it
180676 -           impact others?
180677 -
180678 -    5.  Load the Learning category.
180679 -
180680 -        Each Learning information item is a structured proof or
180681 -        explanation of one Knowledge item. While there may be more than
180682 -        one Learning item for each informaton item, each is linked to
180683 -        and supports only one associated Knowledge item. ref DRT 2 5168
180684 -
180685 -        At this stage the repository is ready for general use. You
180686 -        should be able to view the DKR node map and see the
180687 -        relationships between Goals, Knowledge, and Learning.
180688 -
180689 -        Question...
180690 -           ..
180691 -           Need example or mock up of "node map."
180692 -           ..
180693 -           Need scenario showing entire process applied to say a
180694 -           secretary scheduling a meeting; a doctor planning a knee
180695 -           operation; a home owner fixing the back fence; an engineer
180696 -           coding the DKR.
180697 -
180698 -    6.  Load the user base.
180699 -
180700 -        This is the list of people using the DKR.
180701 -        ref DRT 2 5950
180702 -
180703 -    7.  Begin operation by requesting improvement to Knowledge and
180704 -        Learning items in relation to achieving the DKR Goal(s). In
180705 -        this model, the information flow is that opinions and evidence
180706 -        would be submitted to the Experience category for discussion,
180707 -        then as appropriate, integrated into the Learning and Knowledge
180708 -        categories. ref DRT 2 6992
180709 -
180710 -        As new information items are created, you should be able to
180711 -        view the DKR node map and see the relationship of each item
180712 -        with respect to other Goals, Knowledge, Learning, and
180713 -        Experience items.
180714 -
180715 -        Question...
180716 -           ..
180717 -           Need example and mock up of "node map."
180718 -
180719 -    8.  When sufficient Knowledge is available to actually take action
180720 -        to solve the problem, then the action (exhibition of Wisdom in
180721 -        this example) is taken and the results are recorded. These
180722 -        results are entered info the repository as Experience, to be
180723 -        deliberated upon and incorporated into further refinements of
180724 -        Learning and Knowledge items. ref DRT 2 6138
180725 -
180726 -        Question...
180727 -           ..
180728 -           What is knowledge, and how is it measured to determine
180729 -           sufficiency?
180730 -
180731 -
180732 -
180733 -
180734 -
180735 -
180736 -
180737 -
180738 -