THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net
S U M M A R Y
DIARY: August 31, 2008 02:51 AM Sunday;
Rod Welch
Jack, Morris, Gary debate objectives of Knowledge Management.
1...Summary/Objective
2...Sensemaking Communication Metrics Intelligence Support by SDS
3...Grains Gone Wild Topic Map Example
4...Topic Map Example Applies Dialog Issue Mapping Facilitate Meetings
5...Dialog Issue Topic Maps Graphic Example Improve Personal Memory
........Accurate Memory Big Challenge Aided by SDS
........Sensemaking Understanding Accurate Memory Critical Details
........Forgetting Critical Details Solution Essential for Sensemaking
........Memory Augments Intelligence People Cannot Remember Details
6...Subject Maps New Form of Topic Maps
7...SDS Unique Solution Nothing Else Available for Knowledge Management
8...Topic Maps Difficult to Support with Software Code Not Well Defined
9...Alternate Views Cause and Effect Source Impact Links Helpful for SDS
10...Causation Understand Chronology Subject Index Augments Intelligence
11...Subject Index Augments Intelligence Understand Chronology Causation
12...Market Demand Grows from Awarness Power of Knowledge Within Reach
13...Customers Require Knowledge of Cause Effect from Command and Control
14...Spirit of SDS Explained in POIMS from 20 Years Experience
15...Enjoy Writing Code for Design Aligns with Personal Experience
16...Java SDS Looks Like Professional Document for Information Management
17...Line Numbers Gone Too Difficult Java SDS Application
18...Flexible Structure for Intelligence Difficult with Conventional Editor
19...21st Century Software Engineering Can Be Advanced with SDS
20...Design Morris Windows Application Search Mapping Plug-ins XML Records
21...Research SDS Unique Design Integreate Personal Organizational Memory
22...Giving Up on Knowledge Management Disappointed SDS Effective
23...Knowledge Management Difficult Not Enough Knowledge Using Information
24...SDS Design Complex Difficult Without Basic Elements Proven Effective
ACTION ITEMS..................
Click here to comment!
1...In some sense, that *is* an issue for SDS records. Were Rod to
CONTACTS
SUBJECTS
What Are We Trying to Accomplish SDS Develop Windows Version Knowled
0503 -
0503 - ..
0504 - Summary/Objective
0505 -
050501 - Follow up ref SDS 37 0000, ref SDS 36 0000.
050502 -
050503 -
050504 -
050505 -
050507 - ..
0506 -
0507 -
0508 - Progress
0509 -
050901 - Morris indicated in a recent conference call which included Gary, that
050902 - he has started over again on the SDS program using Java and SQL. He
050903 - expressed concern that SDS has too many functions. He cannot find
050904 - space on the program presentation window to display all of the buttons
050905 - to execute SDS functions.
050907 - ..
050908 - There is continuing debate about the purpose and use of the SDS
050909 - program he is developing for Windows. On 080318 he explained tracking
050910 - the record of health care to recover from medical maladies in a small
050911 - vest pocket notebook. ref SDS 33 9G6U
050913 - ..
050914 - Morris wants to substitute Windows Word programming features for
050915 - tables to replace the current design that uses traditional positioning
050916 - with fixed fonts to construct structures, disucssed on 080606.
050917 - ref SDS 36 NQ4M
050919 - ..
050920 - On 080606 Morris also discussed eliminating line numbers and control
050921 - fields because, like tables, these structures are difficult to program
050922 - using editor technology that flows text to the screen width.
050923 - ref SDS 37 MN5F
050925 - ..
050926 - These plans to eliminate SDS capabilities presents difficulties other
050927 - projects have suffered from not understanding Knowledge Management.
050929 - ..
050930 - Submitted a letter to the team saying...
050931 -
050932 - 1. Subject: SDS Scope Knowledge Management
050933 - Date: Sun, 31 Aug 2008 03:02:53 -0700
050938 - ..
050939 - 2. Dear Jack, Morris, Gary,
050941 - ..
050942 - 3. Correspondence a few weeks ago on Aug 20 (shown below)
050943 - discusses how SDS is used. This inquiry reflects prior
050944 - efforts on the OHS/DKR project with contributors asking over
050945 - many years "What are we trying to accomplish, shown by case
050946 - study on 020530. ref SDS 20 EF7I
050948 - ..
050949 - 4. Difficulty nailing down purpose and scope has frustrated past
050950 - projects transitioning from building "information" to a new
050951 - paradigm of knowledge tools.
050953 - ..
050954 - 5. Jack presents a process of "sensemaking," cited earlier in his
050955 - letter on 040622 discussing complexity theory. ref SDS 25 FM5W
050957 - ..
050958 - 6. In the recent letter, Jack lists elements of sensemaking...
050959 -
050960 - 1. foraging
050961 - 2. filtering
050962 - 3. annotating
050963 - 4. tagging
050964 - 5. connecting
050965 - 6. discourse
050967 - ..
050968 - 7. "Foraging" is described as searching the Internet for stuff.
050970 - ..
050971 - 8. Jack says in part that "Rod's records seem much closer to
050972 - reactive tomes associated with emails such as this one, and to
050973 - events that occur in his life. I can see how Boeing and others
050974 - might benefit from reactive records."
050976 - ..
050977 - 9. Morris says in part that "Rods records are primarily from
050978 - introspection. His foraging seems to be only as a justification
050979 - of his position. I see very little records where he collects
050980 - data and then draws conclusions."
050982 - ..
050983 - 10. There are 30,000 SDS records. Some contain research on the
050984 - Internet, as Jack notes, some are reflective, and
050985 - introspective, cited by Morris. On 911123 Morris explained SDS
050986 - as a "new way of working," ref SDS 3 0477, that is different
050987 - from what he calls "feel good management." ref SDS 3 1331
050989 - ..
050990 - 11. SDS foundational documents provide a starting point for
050991 - discussing elements and purpose of SDS. For example,
050992 - "Intelligence support" to organize, analyze, align, summarize
050993 - and verify accuracy with feedback loops is explained in POIMS.
050994 - ref OF 3 0367
050996 - ..
050997 - 12. "Organize, analyze, align, etc" are well recognized tasks
050998 - people perform and discuss. So, this is a good place to start
050999 - on understanding SDS.
051001 - ..
051002 - 13. The SDS "plan, perform, report" design, is also explained in
051003 - POIMS. ref OF 6 6649
051005 - ..
051006 - 14. These elements are described with some detail in the list of 8
051007 - steps using SDS for Communication Metrics. ref OF 6 685K
051009 - ..
051010 - 15. Jack's list is fine too. If it is easier talking about
051011 - foraging and filtering, etc., this can certainly lead to
051012 - effective tools.
051014 - ..
051015 - 16. The gravamen of concerns in the recent correspondence centers
051016 - on the quality of presentation in my records. Typical records
051017 - synthesize related events, multiple discussions, documents, and
051018 - research, toward making sense of complex work, illustrated by
051019 - the record on August 21. ref SDS 38 0000
051021 - ..
051022 - 17. A constructive exercise would be to propose how this record can
051023 - be revised to strengthen "sensemaking" toward saving lives,
051024 - time, and money?
051026 - ..
051027 - 18. What tools are needed to do the work?
051029 - ..
051030 - 19. Morris asked about research reported in SDS?
051032 - ..
051033 - 20. An example is the record on 040517 discovering life threatening
051034 - conditions, and evaluating what can be done about it.
051035 - ref SDS 24 YN3L
051037 - ..
051038 - 21. Another example a few months earlier on 040312 reviewed the
051039 - "locality principle" that drives the "power of knowledge."
051040 - ref SDS 23 YH4G
051042 - ..
051043 - 22. History of Knowledge Management as a new buz word, was reviewed
051044 - on 011102. ref SDS 19 DT5F
051046 - ..
051047 - 23. Research on "hard work" required to perform "Knowledge
051048 - Management" using conventional tools, reported on 000307.
051049 - ref SDS 10 4472
051051 - ..
051052 - 24. Wicked problems that present knowledge management dilemmas when
051053 - complexity masks causation was reviewed on 060722. ref SDS 26
051054 - 346F
051056 - ..
051057 - 25. How then can we extend and improve ability to do this work?
051058 -
051064 -
051065 -
051067 - ..
0511 -
0512 -
0513 - Morrs and Jack comment on SDS
0514 -
051401 - Morris submitted a letter on 080820 commenting on Jack's ideas about
051402 - Knowledge Management and SDS design for intelligence support...
051403 -
051404 - 1. August 20, 2008
051405 - Subject: Subject Index description
051406 - Date: Wed, 20 Aug 2008 13:51:12 -0700
051414 - ..
051415 - 2. My observation is Rods records are primarily from
051416 - introspection. His foraging seems to be only as a
051417 - justification of his position. I see very little records where
051418 - he collects data and then draws conclusions. I see more places
051419 - where he made conclusions and adds remotely related and often
051420 - marginal support.
051422 - ..
051423 - Morris comments on Jack's discussion of SDS applied to Knowledge
051424 - Management for "sensemaking" where he describes a process of
051425 - "foraging" on the Internet.
051427 - ..
051428 - Morris' letter to the team continues...
051429 -
051430 - 3. The records show very little collaboration where he examines
051431 - the data with others, and draws from multiple views to form a
051432 - thesis. They show a lot of adversarial activities where he
051433 - crafts a record to support his desired outcome in spite of the
051434 - "sense" of the position. (This may be from his employment in
051435 - the construction claims management area which is highly
051436 - adversarial).
051438 - ..
051439 - Collaboration has been a major part of discussions about Knowledge
051440 - Management.
051442 - ..
051443 - Morris' letter to the team continues...
051444 -
051445 - 4. The rest of your sensemaking steps are done manually through
051446 - his introspections in the record. (Otherwise, he would pick up
051447 - the vocabularies common on the web).
051449 - ..
051450 - 5. My first impression is that Rod performs your steps in the
051451 - reverse order. He starts with discourse and automatic linking
051452 - from prior records, and ends up foraging for supporting
051453 - positions on the web. I'm sure there is some interesting
051454 - social science in there somewhere between the two approaches.
051455 - :-)
051457 - ..
051458 - 6. I agree attributes are more important than names, and I feel
051459 - that is how I would locate things. His indexes are modeled on
051460 - work breakdown codes, and having multiple people with the same
051461 - name is not normally much of a problem as the names inherit the
051462 - entire hierarchy in the system. He permutes the descriptions
051463 - and allows multiple descriptions for each WBC entry to permit
051464 - index searching off the hierarchy through the descriptions.
051466 - ..
051467 - 7. I feel the real power in what Rod is doing are the internal
051468 - reflections placed in the record, and not the indexing he has
051469 - added. This is more an issue of personal discipline than fancy
051470 - programming/linking.
051472 - ..
051473 - 8. Formalizing your steps of sensemaking into the program flow
051474 - could be very useful for those starting out. I will give it
051475 - some thought. What have you done in this area?
051477 - ..
051478 - 9. My limited experience is that visual maps are of limited value
051479 - when they extend past a few screens of information. It is very
051480 - hard to visualize the map importance from the thousands of
051481 - pieces of items linked. Perhaps the industry has made great
051482 - strides in this area. I just haven't seen it yet. (It could be
051483 - my limited engagement with the state of the art).
051485 - ..
051486 - 10. I view it much like PERT charts. (Another form of linked
051487 - relationships in the simplest sense) They look great for a
051488 - simple project, but when you have 100,000 activities they need
051489 - to be printed on paper the size of a football field, and IMHO
051490 - are useless. Hence in most large projects, everyone uses Gantt
051491 - chart lists instead of the visual 2D PERT maps.
051493 - ..
051494 - 11. Thanks for responding,
051495 -
051496 - Morris
051497 -
051498 -
051500 - ..
051501 - Sensemaking Communication Metrics Intelligence Support by SDS
051502 -
051503 - Jack comments on Morris' letter discussing SDS, and Jack describes
051504 - SDS support Knowledge Management.
051505 -
051506 - 1. From: Jack Park [mailto:jack.park@sri.com]
051507 - Date: Wednesday, August 20, 2008 7:48 AM
051512 - ..
051513 - Morris,
051515 - ..
051516 - 2. Many thanks for this explanation.
051518 - ..
051519 - 3. I'm beginning to gather that SDS falls into the rubric known as
051520 - "sensemaking". In my thesis work, I have identified several
051521 - "aspects" of sensemaking:
051522 -
051523 - a. foraging
051524 - b. filtering
051525 - c. annotating
051526 - d. tagging
051527 - e. connecting
051528 - f. discourse
051530 - ..
051531 - 4. It seems that all of those are, in some way, aspects of Rod's
051532 - "algorithm".
051534 - ..
051535 - 5. Foraging? Maybe, maybe not. I haven't spent enough time in
051536 - Rod's records to know if he spends time with google foraging
051537 - for stuff to comment on in SDS records.
051539 - ..
051540 - 6. My experience thus far is that his records seem much closer to
051541 - reactive tomes associated with emails such as this one, and to
051542 - events that occur in his life. I can see how Boeing and others
051543 - might benefit from reactive records.
051544 -
051545 -
051546 -
0516 -
SUBJECTS
Dialog Maps Issue Topic Example Paul Krugman 080407 Grains Gone Wild
1603 -
160401 - ..
160402 - Grains Gone Wild Topic Map Example
160403 - Topic Map Example Applies Dialog Issue Mapping Facilitate Meetings
160404 - Dialog Issue Topic Maps Graphic Example Improve Personal Memory
160405 -
160406 -
160407 - 7. What I am beginning to think is that a dialogue/issue map e.g.
160408 -
160409 - http://compendium.open.ac.uk/
160410 -
160411 - ...is the kind of map that would paint, visually, the causal
160412 - chains in SDS records. Each node in such a map can be treated
160413 - as, itself, a unique topic, one that happens to circumscribe
160414 - potentially many other topics--those which are entailed in the
160415 - dialogue itself.
160417 - ..
160418 - See next record segment for local access. ref SDS 0 H68I
160420 - ..
160421 - Jack's letter to Gary on 071222 provided extensive explanation of
160422 - Subject Maps, Topic Maps, schemas, etc. ref SDS 30 1G5N
160423 -
160424 -
160425 -
160426 -
1605 -
SUBJECTS
Default Null Subject Account for Blank Record
1703 -
170401 - ..
170402 - Accurate Memory Big Challenge Aided by SDS
170403 - Sensemaking Understanding Accurate Memory Critical Details
170404 - Forgetting Critical Details Solution Essential for Sensemaking
170405 - Memory Augments Intelligence People Cannot Remember Details
170406 -
170407 -
170408 - Jack's letter continues...
170409 -
170410 - Since I cannot recall if I did this before (not being an SDS
170411 - user and suffering the ravages of CRS (can't remember sh*t, aka
170412 - somezheimers), I'm attaching an issue map I made to tease the
170413 - structure out of a Paul Krugman OpEd in nytimes.com online.
170414 -
170415 -
170417 - ..
170418 - 8. I don't think that issue mapping necessarily helps in the
170419 - primary task of SDS records: recall, but I do think it plays an
170420 - enormous role in sensemaking.
170422 - ..
170423 - Jack makes a good point about using connections in a flow diagram to
170424 - help make sense of complexity. SDS supports chronology, context, and
170425 - connection, explained in POIMS. ref OF 6 8555
170427 - ..
170428 - Flow diagrams identify "subjects," which play a significant role
170429 - supporting accurate "recall" of personal and organizational memory.
170430 - POIMS describes SDS support for finding critical details by
170431 - remembering only the gist of the story. ref OF 6 KH8J
170433 - ..
170434 - Accurate personal and organizational memory of critical details aids
170435 - ability to make sense of complex daily work. Morris commented that
170436 - remembering dates for understanding chronology is difficult; he cited
170437 - self-evident benefits of links that improve memory by orders of
170438 - magnitude, reported on 940327. ref SDS 5 J496 Later, on 950228 Morris
170439 - suggested using SDS to improve productivity of meetings with accurate
170440 - memory of work history. ref SDS 6 1994
170442 - ..
170443 - Concern about poor memory is universal on details that occurred in the
170444 - past. Memories fade if not regularly reinforced. On 071222 Morris
170445 - forget "essential features" of SDS had been submitted on several prior
170446 - occassions. ref SDS 29 3V35 On 080318 people cannot find letters
170447 - stored on computers in Microsoft Outlook directories, and in time to
170448 - get things done, ref SDS 33 GZ7J, even using search and computer
170449 - indexing. technologies. ref SDS 33 0R6G On 080606 Morris asked for
170450 - SDS use cases again, underscoring poor productivity using conventional
170451 - tools that reduce productivity finding critical details. ref SDS 37
170452 - 9Z4H
170454 - ..
170455 - Jack submitted the issue map received again today, in a prior letter
170456 - received on 080506. ref SDS 35 Y49Y At that time, he noted the file
170457 - could not be displayed on the Internet. ref SDS 35 OU4N Today, he
170458 - provides a link to the Internet, and does not repeat restrictions, so
170459 - evidently display on the Internet has subsequently been approved.
170461 - ..
170462 - Jack reported on 010411 that SDS enables remembering "every little
170463 - thing." ref SDS 16 X34F Last year on 070913 Jack described SDS
170464 - support enabling "Elephant memory."
170465 - A few weeks later on 010425, Morris made the
170466 - same point that SDS provides a "utopia" compared to other tools for
170467 - finding everything in the right place at the right time. ref SDS 17
170468 - EP7F Earlier on 990721 Morris suggested explaining SDS for helping
170469 - people remember chronology accurately. ref SDS 8 MG3L
170470 -
170471 -
170472 -
170473 -
1705 -
SUBJECTS
Default Null Subject Account for Blank Record
1803 -
180401 - ..
180402 - Subject Maps New Form of Topic Maps
180403 -
180404 -
180405 - Jack's letter continues...
180406 -
180407 - 9. Topic maps have come a long way since the 80's. They really
180408 - became a standard late in the 90's with ISO 13250, originally
180409 - an SGML spec, created by Steve Newcomb, the inventor of the
180410 - SGML standard Hytime, used now to design airplanes and more.
180411 - Today, topic maps have morphed to something even different; we
180412 - use the term "subject map" to differentiate the latest thinking
180413 - from the SGML/XML topic maps, though subject maps are still
180414 - topic maps as per the ISO standard. I've even implemented
180415 - subject maps in OWL.
180417 - ..
180418 - Jack's letter to Gary on 071222 provided extensive explanation of
180419 - Subject Maps, Topic Maps, schemas, etc. ref SDS 30 1G5N
180421 - ..
180422 - Jack's letter continues...
180423 -
180424 - 10. Basically, what it means to say "topic map" is to entail the
180425 - principle of co-location: you are saying that you are committed
180426 - to the idea that your database will be "extremely normalized",
180427 - that there is one and only one place (location) you need to go
180428 - to find all that is knowable about a particular subject.
180430 - ..
180431 - 11. This places a burden on the notion of subject identity that
180432 - goes way beyond the simple ramblings of the semantic web: a
180433 - single URI should suffice to identify a subject. Sure, it
180434 - should, but it won't because nobody can agree on which URI to
180435 - use for each subject, and others will have no clue which URI
180436 - goes with which subject: this isn't a problem for google.
180438 - ..
180439 - 12. We will always need representations of those properties
180440 - (attributes) of each subject that people commonly use to
180441 - identify their subjects. Names, alone, won't do it. That's
180442 - topic mapping.
180444 - ..
180445 - 13. In some sense, that *is* an issue for SDS records. Were Rod to
180446 - start talking about the Jack Park that writes baseball books,
180447 - he'd likely be in deep bandini rather quickly.
180448 -
180452 -
180453 -
180454 -
1805 -
SUBJECTS
Default Null Subject Account for Blank Record
1903 -
190401 - ..
190402 - SDS Unique Solution Nothing Else Available for Knowledge Management
190403 -
190404 - Morris comments on letters from Jack and Gary explaining SDS support
190405 - Knowledge Management.
190406 -
190407 - 1. Subject: Subject Index description
190408 - Date: Tue, 19 Aug 2008 22:29:31 -0700
190413 - ..
190414 - 2. Jack, et al
190416 - ..
190417 - 3. Rod has a tendency to redefine common words, and his claims
190418 - often seem to be from lack of experience with what else is out
190419 - there. He drive me nuts with alphabet technology,
190420 - communication metrics involving no measurements and other
190421 - terms.
190423 - ..
190424 - Morris cites research of other tools and methods below seems to yield
190425 - no other solution for Knowledge Management. ref SDS 0 925T
190427 - ..
190428 - Morris' letter to the team continues...
190429 -
190430 - 4. The subject index is a user maintained index. As far as I can
190431 - see, the only novel thing he does is inherit subjects each time
190432 - he spawns a record from a prior record. This makes life
190433 - easier, but I think there are many weak links in the record
190434 - over time. Perhaps some day there will be so many weak
190435 - links/subject index entries it will make finding things no
190436 - better than a good search engine limited to the set of records.
190438 - ..
190439 - How many days does it take to test out a system to assess viability in
190440 - relation to concerns for "weak links/subject index entries? SDS has
190441 - been used for going on 30 years, noted by Morris below. ref SDS 0 929U
190442 -
190443 - 30 x 365 = 10,950 days
190445 - ..
190446 - That's a lot days to worry about maybe "someday" a broken link might
190447 - occur or the subject index can't find something. Right now everyday
190448 - everybody has problems finding anything using other tools, reported by
190449 - Morris on 960406. ref SDS 7 4249 Later, 020822 Ray Ozzi, who
190450 - developed Lotus Notes, and later Groove, noted that people are feeling
190451 - "pain" trying to find information. ref SDS 21 Q99G Bill Gates planned
190452 - to solve the problem on 021108. ref SDS 22 EF5I On 010411 Jack Park
190453 - noted SDS enables finding "every little thing." ref SDS 16 X34F
190455 - ..
190456 - Morris noted the same thing on 010425, describing SDS as a utopia
190457 - compared to other tools. ref SDS 17 EP7F
190459 - ..
190460 - There are about 30,000 records, and perhaps 4 million subjects. This
190461 - has proven effective finding specific information and for assembling
190462 - chronologies of history on specific subjects, based on remembering the
190463 - "gist of the story," as set out in POIMS. ref OF 6 16EF
190465 - ..
190466 - Morris' letter to the team continues...
190467 -
190468 - 5. It's value is what the user puts into it IMHO. I feel most
190469 - people will not use it to Rod's extent. (I'm sure he has
190470 - invested thousands of hours to come up with 3 million entries).
190471 - A good search engine is a help at the worst, and the answer to
190472 - the issue at best.
190474 - ..
190475 - This is a good thought. Many people can benefit from a good search
190476 - engine. On 080206 Morris was considering a search engine for SDS
190477 - because the editor he proposes does not work well with the Subject
190478 - Index. ref SDS 32 RT4J At that time he noted there is no record of
190479 - marketing studies that show people like the SDS Subject Index, and a
190480 - lot of people are using search engines. ref SDS 32 CV9N Earlier on
190481 - 071220 Jack proposed Apache Solr search engine. ref SDS 28 TX5U A few
190482 - days later on 071222, Jack submitted an explanation of Apache Solr
190483 - search engine used for a Subject Map. ref SDS 30 4J4K
190485 - ..
190486 - SDS is designed for intelligence support using 8 steps of
190487 - Communication Metrics listed in POIMS. ref OF 6 685K One of those
190488 - steps is context management.
190489 -
190491 - ..
190492 - Topic Maps Difficult to Support with Software Code Not Well Defined
190493 -
190494 -
190495 - Morris' letter to the team continues...
190496 -
190497 - 6. It's not hard to add the basic index, but I don't think it is
190498 - really going to be a topic map. I don't feel the industry has
190499 - a good definition for a topic map. I have heard the term since
190500 - the 1980's with various definitions and features.
190501 -
190503 - ..
190504 - Alternate Views Cause and Effect Source Impact Links Helpful for SDS
190505 -
190506 -
190507 - That said, the SDS system lacks most things I consider part of
190508 - a map like pivot and alternate view abstractions except by user
190509 - permutations. It also has no cause and effect or source and
190510 - impact type linkages and contribution weights.
190512 - ..
190513 - I expect a good topic map to have a nice flow back to premise
190514 - causes and forward flow to future impacts/results in the map.
190515 - I expect a topic map to reach related areas by traversing flows
190516 - around a region of interest showing and finding relationships
190517 - by link traversals and context weighting.
190519 - ..
190520 - An example of such a system, and record showing application would be
190521 - helpful to guide discussion and formulate code to implement.
190523 - ..
190524 - Useful "expectations" of knowledge tools require experience working
190525 - for a long period with the tools. Morris started on 910520 with
190526 - initial strong insights. ref SDS 2 I66F The early version of SDS was
190527 - difficult to learn without help, and Morris did not have time to get
190528 - help, reported on 920215, ref SDS 4 5820, because his company
190529 - downsizing required relying on existing skills, rather than investing
190530 - time to learn a new way of working. ref SDS 4 5774
190531 -
190533 - ..
190534 - Causation Understand Chronology Subject Index Augments Intelligence
190535 - Subject Index Augments Intelligence Understand Chronology Causation
190536 -
190537 -
190538 - Morris' letter to the team continues...
190539 -
190540 - Rod's SDS flow exists only in one direction through record
190541 - citation, and not by the subject index. IMHO the index is
190542 - merely a user index to help organize the records according to
190543 - personal taste. It's value is completely at the mercy of the
190544 - user, and little is a direct result of program smarts, except
190545 - perhaps assistance in performing permutations and sub mapping
190546 - copies. Rod makes significant use of and time investment in
190547 - the index and therefore finds it useful. (I'm sure there's
190548 - circular reasoning in there somewhere).
190550 - ..
190551 - Augmenting intelligence with precision access to "routinize" good
190552 - management begins with command and control of the record according to
190553 - personal taste, see POIMS. ref OF 3 015M Peter Drucker called for
190554 - technology to make good management "routine," in an article published
190555 - by Atlantic Monthly, reviewed on 991025. ref SDS 9 0785 The subject
190556 - index enables "precision access" by constructing and assigning the
190557 - organic structure of context to daily work, see POIMS. ref OF 6 8555
190559 - ..
190560 - The scope of "precision access" with the subject index is set out in
190561 - NWO. ref OF 13 PX6J Experience using SDS helps understand the power
190562 - of knowledge from connecting cause and effect expressed in the
190563 - locality principle, reviewed on 040312. ref SDS 23 YH4G
190565 - ..
190566 - Organizing records to understand cause and effect within contextual
190567 - frameworks according to personal taste supports requirements for
190568 - personal and organizational memory by applying common standards, e.g.,
190569 - contracts, specifications, schedules, budgets, work history. See
190570 - explanation of "organizational memory" in POIMS. ref OF 5 1101
190571 -
190572 -
190574 - ..
190575 - Market Demand Grows from Awarness Power of Knowledge Within Reach
190576 - Customers Require Knowledge of Cause Effect from Command and Control
190577 -
190578 -
190579 - Morris' letter to the team continues...
190580 -
190581 - 7. As far as a product goes, there is very little customer
190582 - requirement market input, user skill level mapping, work flow
190583 - analysis, or focus group tests. There are no user activity
190584 - priorities and function distribution statistics. Rod knows
190585 - what he likes, and thinks few others understand knowledge,
190586 - writing, or the alphabet :-). He produces records, and this is
190587 - his test of a system.
190589 - ..
190590 - Routine creation of work product is a simple test of usability and
190591 - utility. If production of records is not efficient, the tools will
190592 - not be used.
190593 -
190595 - ..
190596 - Spirit of SDS Explained in POIMS from 20 Years Experience
190597 - Enjoy Writing Code for Design Aligns with Personal Experience
190598 - Java SDS Looks Like Professional Document for Information Management
190599 -
190600 -
190601 - Morris' letter to the team continues...
190602 -
190603 - 8. I enjoy writing code, and am trying to fashion something that
190604 - meets the spirit of SDS. It may or may not be to Rod's liking
190605 - as the function keys are not required to do things, and it
190606 - works with windows normal keyboard mapping. At least it will
190607 - feel like a windows based application.
190609 - ..
190610 - This aligns with the meeting on 080206 when Morris demonstrated using
190611 - initial code for SDS Windows application. ref SDS 32 RR47
190613 - ..
190614 - The purpose of SDS is explained in the introduction to POIMS.
190615 - ref OF 3 6221
190617 - ..
190618 - Windows should make SDS widely available rather than diminish
190619 - functionality and efficient usability for working intelligently.
190620 -
190622 - ..
190623 - Line Numbers Gone Too Difficult Java SDS Application
190624 - Flexible Structure for Intelligence Difficult with Conventional Editor
190625 -
190626 -
190627 - Morris' letter to the team continues...
190628 -
190629 - The Java swing editor toolkits make writing an editor
190630 - unnecessary, and are close to a MVC architecture. The line
190631 - numbers are gone. It now reformats to screen sizes through the
190632 - layout manager, and dates can be picked from dialogs and are
190633 - displayed in the local locale, etc. I hope Rod can recover
190634 - from not having a record that looks like a phone bill from
190635 - 1964. It should look like a professional document. I have
190636 - told him that fixed fonts are not a requirement, there are no
190637 - fixed lines, and until he is writing the code, it will stay
190638 - that way.
190640 - ..
190641 - SDS design requirements replace the paradigm of "documents" with a new
190642 - model of "Knowledge Management," explained in POIMS. ref OF 4 K84L
190643 -
190644 - [On 081120 Gary raised concerns about difficulty designing
190645 - SDS line numbers for flexible record structure, ref SDS 39
190646 - 5O67, reflecting difficulty creating Knowledge Management
190647 - at Microsfot, IBM, Oracle -- SDS advantage arises from
190648 - having solved this difficulty, essential to advance from
190649 - information to a culture of knowledge to integrate personal
190650 - and organizational memory and management (POIMS).
190651 - ref SDS 39 PV6F
190653 - ..
190654 - Requirements for flexible structures are reviewed on 890523.
190655 - ref SDS 1 P13O
190657 - ..
190658 - Strong emotional resistance to flexible structures using line numbers
190659 - for precision access was evident in initial work product submitted on
190660 - 080124. ref SDS 31 H19U This further aligns with the conference call
190661 - on 080606. At that time, Gary and Morris discussed SDS without
190662 - shallow outline using line numbers for flexible structures that enable
190663 - precision access. ref SDS 37 9A5Q SDS design for precision access is
190664 - set out in NWO listing the scope for intelligence support. ref OF 13
190665 - PX6J Earlier on 071220, Jack Park submitted an example using SDS line
190666 - numbers for precision access, ref SDS 28 PK5J, explained in the record
190667 - on 890523, ref SDS 1 5C6L,
190669 - ..
190670 - Powerful cultural forces from long experience with popular writing
190671 - technologies convinces people that flexible structures are not popular
190672 - and so not required for command and control of the record, reviewed on
190673 - 080206. ref SDS 32 1L6O Limited time prevents review of credible
190674 - analysis on improving the established publishing paradigm. These
190675 - pressures inoculate against performing hard work in the beginning to
190676 - create tools that save lives, time, and money. ref SDS 32 6F9G
190678 - ..
190679 - The editor is the core of SDS for advancing alphabet technology by
190680 - adding dimensions for time and context to conventional literacy. SDS
190681 - record are not "documents." These records support Knowledge
190682 - Management that augments intelligence for command and control of daily
190683 - work that comprises a continuous information stream, which includes
190684 - documents. The "look" is distinguished from professional documents by
190685 - adding flexible structure to manage time and context. Morris did a
190686 - good job for many years collaborating to refine unique editor support
190687 - that enabled creating effective intelligence support, reported on
190688 - 000723. ref SDS 12 5W6N
190690 - ..
190691 - The letter today aligns with the meeting on 080206. At that time,
190692 - Morris explained plans for using a commercial grade editor to bring
190693 - SDS into the 21st century. ref SDS 32 HE6N Adopting a design that
190694 - floats the right margin makes creating SDS flexible structures,
190695 - including line numbers, Control Fields, Subjects, Contacts,
190696 - References, and linking, all very difficult to support. This yields
190697 - another wordprocessing program like Kaiser, Lotus Notes, Outlook,
190698 - Sharepoint, Word, etc., rather than Knowledge Management for
190699 - intelligence support, and Communication Metrics. ref SDS 32 ND8N
190701 - ..
190702 - Morris explained on 080206 that creating the SDS design is difficult.
190703 - ref SDS 32 QM6H He enjoys using Java to develop code for commonly
190704 - used tools. ref SDS 32 RR36
190706 - ..
190707 - Gary's SDS record on 080425 commented that line numbering to provide
190708 - verticle forms could be accomplished without line numbers by using a
190709 - tagging system, reviewed on 080426. ref SDS 34 5Q7O
190711 - ..
190712 - Tools for creating professional documents are essential. SDS strives
190713 - to advance a theory of knowledge that integrates documents with other
190714 - sources for better command and control of daily work, see POIMS.
190715 - ref OF 7 1113 Line numbers provide a lot of support SDS objecitves
190716 - distinguished from traditional document formats, explained on 080426,
190717 - ref SDS 34 S14M, and citing background on 080523. ref SDS 1 5C6L
190718 -
190720 - ..
190721 - 21st Century Software Engineering Can Be Advanced with SDS
190722 - Design Morris Windows Application Search Mapping Plug-ins XML Records
190723 -
190724 -
190725 - Morris' letter to the team continues...
190726 -
190727 - 9. The indexes and user contexts are maintained in MYSQL (or any
190728 - other SQL database could be used) and can be local, on a
190729 - server, or over the web. Imports from other tools to the
190730 - indexes should be relatively easily. I'm expecting other
190731 - search and mapping tools to be available in the future. Flow
190732 - to and from record links should be straight forward through
190733 - SQL. The diary records are in an XML style format for longer
190734 - term use. (One of the niceties of Rod's system is he has
190735 - records back to about 1986 or so, and they are still useable 30
190736 - years later)
190738 - ..
190739 - 10. I consider all this simply writing programs in the 21st
190740 - century.
190742 - ..
190743 - Morris makes a good point. Software engineering can be strengthened
190744 - by developing expertise to create SDS design requirements, and
190745 - applying SDS to routinize good management, called out by Drucker.
190747 - ..
190748 - Morris' letter to the team continues...
190749 -
190750 - 11. All input is valuable, and I appreciate your experience and
190751 - wisdom. Re-inventing the existing is not the goal. Focusing
190752 - on a basic problem solution may be a benefit to finding
190753 - something useful. Those aware of better solutions or other
190754 - adjuncts are always invited to provide input.
190756 - ..
190757 - Jack has experience working with SDS beginning at SRI in 2000, when he
190758 - regularly encountered SDS work product. Case study on 071220 shows
190759 - Jack's experience yielded strong support for SDS design. ref SDS 28
190760 - M53N
190761 -
190762 -
190764 - ..
190765 - Research SDS Unique Design Integreate Personal Organizational Memory
190766 -
190767 -
190768 - Morris' letter to the team continues...
190769 -
190770 - 12. I looked at several journal keeping systems, and noted most
190771 - were little better than a wiki. (Perhaps because people mostly
190772 - just write a stream of thought) My first stab at the problem
190773 - was a SQL based wiki like web application through ruby on
190774 - rails. It has some issues in user interface and index usages.
190775 - (Lots of AJAX programming to get reasonable editor type
190776 - interfaces with link management)
190778 - ..
190779 - 13. Outlining systems appeared to provide little historical flow
190780 - and focused on document/project organization.
190782 - ..
190783 - 14. Note taking systems lacked the flow tracking and scheduling.
190785 - ..
190786 - 15. The closest thing I thought about was using one of the revision
190787 - control and bug tracking systems, but felt few people would
190788 - like the differencing and version management concepts. (records
190789 - become problem reports with follow up and tracking).
190791 - ..
190792 - SDS design evolved from experience using SDS for the past 20 years.
190793 - On 010924 Morris noted SDS is unique because design benefits from
190794 - correlation between use and design. ref SDS 18 NK4J
190796 - ..
190797 - What analysis has been done of Morris' research on journal, outline,
190798 - note tracking, revision control and bug tracking systems. How has
190799 - this research been correlated to SDS design objectives, and to the
190800 - code Morris has developed?
190801 -
190803 - ..
190804 - Giving Up on Knowledge Management Disappointed SDS Effective
190805 - Knowledge Management Difficult Not Enough Knowledge Using Information
190806 - SDS Design Complex Difficult Without Basic Elements Proven Effective
190807 -
190808 -
190809 - Morris' letter to the team continues...
190810 -
190811 - 16. I'm sure things could be done better, but am not sure how at
190812 - the moment.
190814 - ..
190815 - Morris' experience of not being sure how to accomplish SDS
190816 - requirements by setting aside elements that enabled the current
190817 - design, per above, ref SDS 0 O37U, follows the path at Microsoft, IBM,
190818 - SRI, Oracle, CRIT, where transformation from information to knowledge
190819 - tools foundered for reasons reported by Eric Armstrong on 001122,
190820 - ref SDS 13 0001, and continuing analysis of complexity that makes
190821 - Knowledge Management hard to design using "information" technologies,
190822 - reported on 001126. ref SDS 15 0001
190824 - ..
190825 - On 000615 the team at SRI reported there wasn't enough knowledge to
190826 - develop Knowledge Management, and so gave up. ref SDS 11 6271 This
190827 - was confirmed on 001126, when the team decided not to consider SDS,
190828 - and instead to use email for developing ideas about Knowledge
190829 - Management. ref SDS 14 QW8I Practices were planned to avoid SDS by
190830 - adding links to email, called out by Doug Englebart. ref SDS 14 XV8L
190831 - Seven years later, the group gave up, having never linked anything.
190832 -
190833 -
190837 -
190838 -
190839 -
190840 -
190841 -
190842 -
190843 -
190844 -
190845 -
190846 -
190847 -
1909 -