CONTACTS 

SUBJECTS
SDS Windows Application Design Review Correspondence Prior Considera

1603 -
1603 -    ..
1604 - Summary/Objective
1605 -
160501 - Follow up ref SDS C0 0000. ref SDS B9 0000.
160502 -
160503 - Focused today on requirements for flexible record structure to create
160504 - efficient usability. ref SDS 0 W889  Discussed prospects for combining
160505 - records and program code with everything in memory; may present design
160506 - issues for linking external records, backup, and managing distribution
160507 - on the Internet. ref SDS 0 058J  Gary reviewed the current design that
160508 - separates records from program code into a collection of files that
160509 - are read as needed. ref SDS 0 0593  Morris requested an explanation of
160510 - a "record." ref SDS 0 KO4F  Plans were considered for "records" with
160511 - nested, collapsable fields to replace line numbers. ref SDS 0 GI9I
160512 - Morris will experiement further with code approaches to test using XML
160513 - for flexible structures, including Control Fields. ref SDS 0 ST3J
160514 - POIMS explains the SDS vision. ref SDS 0 Z48H  Background on earlier
160515 - efforts to use XML technology for Knowledge Management was reviewed.
160516 - ref SDS 0 LY6X  SDS Subject Index was examined briefly during the
160517 - meeting.  SDS Control Fields create record segments that define scope
160518 - assembling related content showing chronology of cause and effect,
160519 - which is different from keyword search methods for indexing files,
160520 - popularized by Google on the Internet. ref SDS 0 ZJ3H  Morris noted
160521 - that granular indexing for command and control of the record is
160522 - tedious.  Not every user requires Context Management. ref SDS 0 X38O
160523 - Morris asked for examples of SDS saving lives time and money.
160524 - ref SDS 0 IB7N  Plan to follow up meeting in about 6 weeks.
160525 - ref SDS 0 JR97
160526 -
160527 -
160528 -
160529 -
160531 -  ..
1606 -
1607 -
1608 - Background
1609 -
160901 - Review Prior Meeting for Common Understandings Not Performed
160902 -
160903 - Follow up ref SDS C0 V35O, ref SDS B9 V35O.
160904 -
160905 - Morris has received correspondence between Jack and Gary collaborating
160906 - on ideas for SDS, listed on 070914, ref SDS B6 QC5H, and cited during
160907 - the meeting last week on 071106. ref SDS B9 5Q3K
160909 -  ..
160910 - We went for a walk 3 - 4 miles again this morning and continued
160911 - discussion on 071113 about contacts, and beginning discssion of SDS
160912 - records, and subjects. ref SDS C0 FL3F
160913 -
160914 -    1.  Prior meeting on...
160915 -
160916 -               070907........................... ref SDS B3 0001
160917 -               071106........................... ref SDS B9 0001
160918 -               071113........................... ref SDS C0 0001
160920 -         ..
160921 -    2.  Reviewed contacts data structures in the record on 071106.
160922 -        ref SDS B9 0R4H
160924 -         ..
160925 -        Reviewed prior work on 071113. ref SDS C0 O65H
160927 -         ..
160928 -        See discussion below. ref SDS 0 O65H
160929 -
160930 -
160931 -
160932 -
160933 -
160934 -
1610 -

SUBJECTS
Memory SDS Records Integrated with Program Code Not Separate on Disk

3703 -
370401 -  ..
370402 - SDS Program Features Morris Proposes Abandoning Flexible Structure
370403 - Memory SDS Records Integrated with Program Code Not Separate on Disk
370404 -
370405 - Follow up ref SDS C0 W889, ref SDS B9 W889.
370406 -
370407 - Work on 070907, ref SDS B3 JQ88, and again on 071106, ref SDS B9 OS6M,
370408 - shows collaboration to advance from information to knowledge tools is
370409 - difficult, ref SDS B9 OS6M, similar to contentious debates with
370410 - invention of the transistor at Bell Labs in the 1940s, reported on
370411 - 960304. ref OF 16 8D4N
370413 -  ..
370414 - We called and talked to Gary for several hours to collaborate on
370415 - design requirements.
370416 -
370417 -        [On 071222 Morris asks for SDS essential features again.
370418 -        ref SDS C8 3V35
370420 -  ..
370421 - Discussion today shifted focus to SDS records, rather than Contacts.
370423 -  ..
370424 - Morris explained ideas for a generic flexibile structure without line
370425 - numbers that can be applied to SDS records and Contacts. (see below
370426 - for further discussion. ref SDS 0 GI9I)
370427 -
370428 -        [On 071220 example Jack Park using line numbers to orient
370429 -        references in Knowledge Space rather than use links. ref SDS C7
370430 -        XZ6J
370432 -  ..
370433 - Morris seemed to indicate plans for an SDS design that reads and holds
370434 - all the records into memory on program launch, similar to Outlook and
370435 - Netscape email.  He feels this will make program coding easier than
370436 - designing tools that build records in a collection of separate files
370437 - on the disk, like the current design using Medit.
370439 -  ..
370440 - Keeping the entire program and work product in memory presents
370441 - difficulties linking to multiple users and external sources.  Not
370442 - clear how access and connections to records for other people would
370443 - work in a network centric organization contemplated for example at
370444 - Boeing reviewed on 060317. ref SDS A0 P357  On 001018 Eric Armstrong
370445 - reported problems putting everything in memory using XML Java data
370446 - object design. ref SDS 51 TP6O
370447 -
370448 -        [...see below background of problems supporting linking with
370449 -        XML technology. ref SDS 0 GI9I
370451 -         ..
370452 -        [On 071219 Gary comments on challenges trying to develop an SDS
370453 -        program that keeps the entire data structure in memory, rather
370454 -        than managing disk access. ref SDS C6 TN5L
370456 -         ..
370457 -        [On 071222 Morris comments that putting everything in memory
370458 -        may be a problem. ref SDS C8 TM6U
370460 -         ..
370461 -        [On 071222 Gary discusses design of SDS records that builds on
370462 -        experience. ref SDS C8 PB7P
370464 -  ..
370465 - How will records be mapped to transfer and manage on the Internet, if
370466 - everything is one big file?  People don't want to put everything on
370467 - the Internet.  People select what to share, the same way people decide
370468 - what to say and what to withhold as private of everything have in
370469 - their head.  Since we have to construct separate files for storage on
370470 - the Internet, why not make it fast and easy to construct an organized
370471 - collection of files on the local computer, as the current program
370472 - does?
370474 -  ..
370475 - Morris asked how big is the current SDS record for the past 20 years?
370477 -  ..
370478 - Currently there are 46K files in 300 MB for 1 person the past 20
370479 - years, another person for about 8 years, and now Gary the past 4
370480 - years.
370482 -  ..
370483 - Another concern is the amount of time required for daily backups that
370484 - would be unnecessary overkill?
370486 -  ..
370487 - Morris noted expanding size of computer disk storage reduces concern
370488 - about backing up everything, e.g., 300 MB, 2 GB, etc., every day, even
370489 - if only 1 record containing 10K is changed in the data base.
370490 -
370491 -     [On 080224 had to modify interim backup reducing scope of safety
370492 -     because adding 1K of data each days requires 200 MB of storage.
370493 -     ref SDS D4 KP4I
370494 -
370496 -  ..
370497 - Records Management Process of Organizing Collection of Files
370498 - Collection Files SDS Records Organized Directory Flexible Structure
370499 -
370500 - Currently there is a common structure for diary records in the SDS
370501 - data base that is fast and easy to manage as a collection of files.
370502 - This is similar to collections of files for Microsoft programs.
370504 -  ..
370505 - What will replace the flexibile structure of SDS files and records
370506 - management, if everything is in one big file on the computer?
370507 - Similarly, there is a data base of contacts comprised of files for
370508 - individuals and other files for organizations, explained on 071106.
370509 - ref SDS B9 2J8H  SDS manages separate file directories for formal
370510 - correspondence on issued and received documents.  Separate directories
370511 - manage files for things like software code, specifications, books, and
370512 - other publications.  The end of the file occurs below the last line in
370513 - the book, report, letter, etc.  Separate files and directories give
370514 - people flexibility for comprehensive records management, including
370515 - cross-filing, and connections, reviewed on 960322. ref SDS 24 6544
370516 -
370517 -        [On 071222 Morris comments that putting everything in memory
370518 -        may be a problem. ref SDS C8 TM6U
370520 -  ..
370521 - Today, Gary discussed creating separate records, as currently
370522 - implemented, rather than integral to program code, as Morris seems to
370523 - have in mind.  Maintaining the current design of separate files for
370524 - separate records aligns with planning on 071106. ref SDS B9 OG6F  This
370525 - design reduces time and storage capacity required for daily backups.
370526 - It would further implement the strategy of discrete records for events
370527 - in the same way that a letter, a book, a report, etc., are all
370528 - separate files.  Why should a schedule or diary record of a birthday
370529 - party, mowing the lawn, attending a meeting, going to the doctor,
370530 - designing a bridge... be any different from a letter planning a party,
370531 - or an article written about the party, or that a report on lawn mowing
370532 - is spearate from a specification for a lawn mower?  Computer disk
370533 - files seem like a natural, easy medium to render common mental
370534 - divisions essential for context management.
370536 -         ..
370537 -        [On 071222 Gary discusses design of SDS records that builds on
370538 -        experience. ref SDS C8 PB7P
370539 -
370540 -
370541 -
370542 -
3706 -

SUBJECTS
Flexible Structure Generic Design Nested Collapsible Fields Replace

7603 -
760401 -  ..
760402 - Nested Collapsible Records XML Emulate Line Numbers Flexible Fields
760403 - SDS Record Define Flexible Structure Line Numbers Replace Nested Fields
760404 -
760405 - Morris asked for an explanation of an SDS schedule record and a diary
760406 - record.  This was reviewed on 070831 in connection with Gary's letter
760407 - on SDS "units of information." ref SDS B1 FL9G  Review at that time on
760408 - 070831 showed SDS has many information units. ref SDS B1 JM9O
760410 -  ..
760411 - SDS scope and functions were discussed in the record on 070907,
760412 - ref SDS B3 JQ88 and again on 071106, ref SDS B9 OS6M,
760413 -
760414 -     [On 080104 Morris discussed difficulty understanding SDS scope and
760415 -     design; asks why SDS improves productivity, and cites support for
760416 -     memory and diligence using good management practices consistently.
760417 -     ref SDS C9 EM9F
760419 -      ..
760420 -     [On 080127 letter to Morris Jones cites question today on reasons
760421 -     for SDS support for Knowledge Mangement, which has not been
760422 -     accomplished by other technologies; recommends reviewing record on
760423 -     960304 reporting Vannevar Bush vision for using computers to
760424 -     perform electronic records management that sets a good agenda for
760425 -     advancing from information to Knowledge Management. ref SDS D1
760426 -     ON3X
760428 -  ..
760429 - SDS features that enable Knowledge Mangement, intelligence support,
760430 - and Communication Metrics were presented in the record on 070126,
760431 - ref SDS A3 QH8L, leading up to a case study showing difficulty people
760432 - have that causes everyone to give up on Knowledge Management.
760433 - ref SDS A3 IQ5L
760435 -  ..
760436 - Earlier on 040212 reviewed a initial software requirements
760437 - specificaiton (SRS) for SDS records prepared by Gary, ref SDS 86 007W,
760438 - and shown in his record on 040122. ref SDS 85 0001
760440 -  ..
760441 - Morris asked for an explanation of SDS functions.
760443 -  ..
760444 - Considered using the notebook computer to demonstrate functions in
760445 - order to provide experience that makes sense of complex explanations.
760446 -
760447 -     [On 071222 Morris requested essential features again. ref SDS C8
760448 -     3V35
760450 -      ..
760451 -     [On 071222 SDS functions are listed for each feature of SDS.
760452 -     ref SDS C8 6P9J
760454 -      ..
760455 -     [On 080531 Morris prepared an explanation of the design for SDS
760456 -     records to guide development of an SDS Windows application.
760457 -     ref SDS D5 W18O
760459 -      ..
760460 -     [On 080831 difficulty remembering the record of personal
760461 -     and organizational memory cited by Jack Park re-submitting
760462 -     information forgotten in the record. ref SDS D6 H68I
760464 -  ..
760465 - "Records" have been used and understood for 2000 years, since the
760466 - Roman Empire when the practice of "records management" emerged,
760467 - reviewed on 060907. ref SDS A1 777F
760469 -  ..
760470 - SDS records comprise a multi-dimensional Knowledge Space with extended
760471 - grammar that advances traditional two dimensional textual narrative,
760472 - explained in NWO. ref OF 16 CO5U  Granular addressability with line
760473 - numbers, anchors, links, chronology, and Control Fields provide new
760474 - forms of punctuation, structure, and organization that increase
760475 - command and control of traditional free-form narrative.
760477 -  ..
760478 - On 890523 seven (7) elements of flexible structure were identified to
760479 - make management productive using computers. ref SDS 2 TP8O  At that
760480 - time, analysis showed efficiencies of computers for a "paperless
760481 - office" require complementarity of electronic records management,
760482 - granular links, and indexing, integrated smoothly for harmony so that
760483 - that each feature supports the other. ref SDS 2 LV59  On 960304
760484 - Vannevar Bush noted requirements of complementarity to make computers
760485 - productive for daily management. ref SDS 23 GX59
760486 -
760487 -     [On 071219 Gary provides a comprehensive explanation of "SDS
760488 -     records." ref SDS C6 UH4K
760490 -      ..
760491 -     [On 071222 Gary explains SDS records identified by the granular
760492 -     structure of time that complements granular addressability and
760493 -     indexing; command and control at lower levels of organic structure
760494 -     creates Knowledge Space. ref SDS C8 PA6P
760496 -      ..
760497 -     [On 080124 Morris submits initial samples of proposed work product
760498 -     created with new Windows version of SDS, ref SDS D0 FW4J; sample
760499 -     work product omits flexible structure. ref SDS D0 H19U
760501 -      ..
760502 -     [On 080128 recommend Morris review article by Vannevar Bush for
760503 -     understanding SDS requirements. ref SDS D2 M37Y
760505 -  ..
760506 - SDS records are similar to letters people write with a beginning and
760507 - end, shown by the "top of file" and "end of file" lines in Medit
760508 - files.  Line numbers and Control Fields are innovations of "SDS
760509 - records" that enhance traditional application of alphabet technology
760510 - by segmenting written text with organizing structure to associate
760511 - mulitple people and organizations, cost accounts, subjects, and track
760512 - action items. (see NWO. ref OF 16 29VU)  People sometimes frame a
760513 - "subject," write about it, and then send the letter.  A letter sent by
760514 - email has unique date and time.  Content may or may not pertain to the
760515 - subject, and can contain multiple sub-subjects.  SDS records are
760516 - defined by the user writing a description for a task in the Schedule,
760517 - examples are listed on 020708. ref SDS 74 MZ6O  The date and time are
760518 - defined at the time work begins, and SDS records have more complex
760519 - structure, including record segments defined by Control Fields, than
760520 - typical emails, with "email" being a data type of "formal
760521 - correspondence" managed by SDS records.
760523 -  ..
760524 - Flexible record structure enabled by line numbers explained in POIMS
760525 - is a big idea of SDS, ref OF 8 M17I, and citing the record on 890523,
760526 - ref SDS 2 P13O, discussing use of line numbers, ref SDS 2 T1VQ, and
760527 - which Morris is attempting to implement with XML methods for a Windows
760528 - SDS application.
760529 -
760530 -        [On 071220 example Jack Park using line numbers to orient
760531 -        references in Knowledge Space rather than use links. ref SDS C7
760532 -        XZ6J
760534 -         ..
760535 -        [On 080124 Morris objects to flexible structure using line
760536 -        numbers for command and control of the work. ref SDS D0 945F
760538 -  ..
760539 - Background case study considering XML for structured records with
760540 - efficient usability was reported on 071113. ref SDS C0 XC3M
760541 -
760543 -  ..
760544 - Flexible Structure Abandon Line Numbers SDS Windows Application
760545 - Line Numbers Consider Abandoning Flexible Structure Windows Version
760546 -
760547 - Today, Morris explained having limited time to review background in
760548 - the 1945 Bush article, per above, ref SDS 0 863H, due to teaching and
760549 - other duties.  Morris explained experience working with Microsoft
760550 - software programs does not offer convincing evidence that SDS requires
760551 - flexible structures.  He described plans for nested, collapsable
760552 - records to replace line numbers for flexible structure.  This solution
760553 - was posed earlier by Eric Armstrong on 000129. ref SDS 37 PTVQ  On
760554 - 001017 Eric planned release of a solution. ref SDS 49 0001  Problems
760555 - with linking were reported the next day on 001018. ref SDS 51 TP6O
760556 - This may relate to plans for storing data and program code in memory,
760557 - per above. ref SDS 0 058J  On 001122 Eric abandoned this effort.
760558 - ref SDS 54 E47M
760560 -  ..
760561 - Challenges understanding requirements for Knowledge Management are
760562 - discussed above. ref SDS 0 W889
760563 -
760564 -        [On 071222 Morris advises that text fixed column fields make
760565 -        programming simpler and limits fonts and formatting.
760566 -        ref SDS C8 TN5P
760568 -         ..
760569 -        [On 071222 Gary discusses design of SDS records that builds on
760570 -        experience. ref SDS C8 PB7P
760572 -         ..
760573 -        [On 080124 Morris submits sample work product that omits line
760574 -        numbers, ref SDS D0 H19U; case study shows role of flexible
760575 -        structures using line numbers. ref SDS D0 HZ6K
760577 -         ..
760578 -        [On 080124 case study shows everybody frustrated by difficulty
760579 -        designing Knowledge Management tools. ref SDS D0 F25I
760581 -  ..
760582 - Morris showed some code that creates recursive and nested fields
760583 - planned for the system, which is a generic solution for SDS records
760584 - that replaces line numbers for creating flexible fields.
760585 -
760586 -        [On 080104 Morris considering switching to Java and using "data
760587 -        objects" for SDS application. ref SDS C9 OM6G
760589 -  ..
760590 - Previously, on 000709 Bill DeHart explained advantages of SDS record
760591 - flexible structure. ref SDS 46 0784
760592 -
760594 -  ..
760595 - Vision SDS Beginning to Take Form Leading to Product Specification
760596 -
760597 - Morris feels he is forming a stronger understanding toward a vision of
760598 - SDS design.  He will continue to develop and test his ideas for
760599 - nested, collapsable records using XML to replace line numbers for
760600 - flexible structure, including Control Fields, per above. ref SDS 0
760601 - RE5M
760603 -  ..
760604 - In about six (6) weeks, Morris wants to meet OA 080201 for follow up
760605 - review on forming a technology platform to implement SDS theory and
760606 - practice, per below. ref SDS 0 JR97
760608 -  ..
760609 - Analysis on 070913 identified seven (7) ways, ref SDS B4 OF3F, to
760610 - summarize SDS capabilities...
760611 -
760612 -            1.  plan the work and work the plan.
760613 -            2.  integrate people, process, time
760614 -            3.  scientific method:  plan, perform, report.
760615 -            4.  integrate time:  past, present, future
760616 -            5.  integrate chronology, context, connection
760617 -            6.  everything in the right place at the right time.
760618 -            7.  personal organizational integrated memory and management
760620 -  ..
760621 - POIMS explains SDS capabilities frame a vision to expand alphabet
760622 - technology for better intelligence support by integrating time and
760623 - information, ref OF 6 6221; objectives, scope, processes, and
760624 - functionality to integrate personal and organizational memory and
760625 - management are explained...
760626 -
760627 -            1.  people, process, time.................. ref OF 6 015M
760628 -            2.  plan, perform, report.................. ref OF 9 6649
760629 -            3.  past, present, future.................. ref OF 9 1112
760630 -            4.  chronology, context, connection........ ref OF 9 8555
760631 -            5.  8-steps Communication Metrics.......... ref OF 9 685K
760633 -  ..
760634 - Complementarity applying the "plan, perform, report" integrated cycle,
760635 - reviewed on 890523, ref SDS 2 LV59, supports a conscious discipline
760636 - ("scientific method") that leverages subconscious intelligence
760637 - mechanics for converting information into the power of knowledge, see
760638 - POIMS, ref OF 6 0367, as a routine exercise that produces a continuing
760639 - resource, like an encyclopedia of personal and organizational memory,
760640 - see POIMS. ref OF 9 6649  Complementarity hormoniously integrating 7
760641 - elements of flexible strucutre appled through writing with chronology,
760642 - context, and connection make efficiencies of electronic records
760643 - management in the paperless office model productive, also, reviewed on
760644 - 890523. ref SDS 2 P13O
760646 -      ..
760647 -     [On 071222 Morris asks for essential features of SDS; ref SDS C8
760648 -     3V35; elements of 3-layer architecture support the vision for a
760649 -     new way of working intelligently. ref SDS C8 3V4H
760650 -
760651 -
760652 -
760653 -
7607 -

SUBJECTS
XML Editor Efficient Usability Responsive SDS Text DOS Structure Ana

AA03 -
AA0401 -  ..
AA0402 - XML Editor Efficient Usability Essential for Integrated Functionality
AA0403 -
AA0404 - Follow up ref SDS C0 LY6X.
AA0406 -  ..
AA0407 - Requirements for responsiveness and efficient usability that make the
AA0408 - current SDS program fast and easy for getting things done, was noted
AA0409 - during the meeting with Morris on 071113, and in connection with
AA0410 - trying an XML editor to replace Medit. ref SDS C0 446N  Requirements
AA0411 - for high performance executing complementary commands equally with
AA0412 - right and left hands was evident from Morris noting today that subject
AA0413 - indexing for command and control of the work cannot be maintained
AA0414 - without efficient usability that makes context management fast and
AA0415 - easy. ref SDS 0 X38O
AA0416 -
AA0417 -        [On 071219 Gary cites examples of migrating DOS applications
AA0418 -        for Wordperfect and Maxthink illustrating extra care required
AA0419 -        to maintaining efficient usability. ref SDS C6 X16G
AA0421 -  ..
AA0422 - Reviewed case study on difficulties others have experienced trying to
AA0423 - achieve efficient usability with XML editing for Knowledge Mangaement,
AA0424 - Communication Metrics, and intelligence support, listed on 071113.
AA0425 - ref SDS C0 XC3M
AA0434 -  ..
AA0435 - Morris indicated today that Eric Armstrong's problems developing an
AA0436 - XML application for Knowledge Management reported on 001122,
AA0437 - ref SDS 54 0001, do not apply to current considerations.  There was
AA0438 - some consideration today of Ken Holeman's anlaysis of XML in the
AA0439 - record on 001124. ref SDS 55 0001
AA0440 -
AA0441 -        [On 080104 Morris considers switching to Java for programming
AA0442 -        XML to design SDS Windows application. ref SDS C9 OM6Y
AA0444 -  ..
AA0445 - Morris seemed further to indicate that requirements for program
AA0446 - responsiveness with efficient usability discussed on 071113 can be
AA0447 - accomplished with the XML editing tools he plans to develop.
AA0448 - ref SDS C0 446N
AA0449 -
AA0450 -        [On 071222 responsive, efficient usability enabled by function
AA0451 -        keys. ref SDS C8 FO94
AA0452 -
AA0453 -
AA0454 -
AA0455 -
AA05 -

SUBJECTS
Subject Index Filing Tedious Records Management Organic Structure Fa

CA03 -
CA0401 -  ..
CA0402 - Subject Index SDS Unique Application for Context Management
CA0403 - Beyond Reach Subject Index Hard Work Complexity Seems Overwhelming
CA0404 - Context Management Hard Work with Tools for Information Management
CA0405 - Everything Connected in Right Place Right Time Self-evident Benefits
CA0406 -
CA0407 - Follow up ref SDS C0 ZJ3H.
CA0408 -
CA0409 - Morris asked how the Subject Index works?
CA0411 -  ..
CA0412 - Used computer c15 to demonstrate using SDS for organizing the record
CA0413 - with Control Fields, and assembling reports into chronological
CA0414 - history, commonly called "case studies."
CA0415 -
CA0416 -     [On 071222 Morris' letter seems to object to learning Knowledge
CA0417 -     Management from demonstrations using SDS. ref SDS C8 UP8K
CA0419 -  ..
CA0420 - Background on SDS subject index and application through Control Fields
CA0421 - in SDS records was reviewed on 070511. ref SDS A4 LP5J
CA0423 -  ..
CA0424 - On 010425 Morris cited advantages of SDS for organizing the record of
CA0425 - daily work so that everything is in the right place at the right time.
CA0426 - This support provides a "utopia" for records management compared to
CA0427 - other tools. ref SDS 61 EP7F  Context Management using the SDS Subject
CA0428 - Index with chronology, context, and comprehensive connections
CA0429 - implements requirements for a "paperless office" proposed by Vannevar
CA0430 - Bush in 1945 published by Atlantic Monthly to guide development of the
CA0431 - computer age, and reviewed on 960304. ref SDS 23 BE6L  At that time,
CA0432 - Bush envisioned robust indexing that integrates time and context to
CA0433 - assemble case studies. ref SDS 23 368K
CA0435 -  ..
CA0436 - On 021108 Bill Gates planned better support for search tools to
CA0437 - improve productivity. ref SDS 82 EF5I  Since then, searching keywords
CA0438 - has become a "holy grail" of computer productivity, reported on
CA0439 - 070126. ref SDS A3 B366  Morris spent 6 hours or so indexing his
CA0440 - computer on 070625 to implement search technology. ref SDS A7 IE8K
CA0442 -  ..
CA0443 - Keyword search is popular to avoid diligence organizing the record by
CA0444 - filing everything under miscellaneous, reported on 070729. ref SDS A9
CA0445 - HE6N  Resistance to diligence that makes bad management seem
CA0446 - attractive, "like fools gold," was explained by Jack Park on 010908.
CA0447 - ref SDS 65 YF5O
CA0449 -  ..
CA0450 - SDS context management using subject indexing with Control Fields
CA0451 - complements indexing content for direct search to solve following
CA0452 - problems...
CA0453 -
CA0454 -            Indexing content slow............. 050516, ref SDS 98 BQ68
CA0455 -            Indexing content slow............. 070625, ref SDS A7 IE8K
CA0456 -            Search index content failed....... 050516, ref SDS 98 HJ49
CA0457 -            Search alone commingles results
CA0458 -            everthing is a hopeless
CA0459 -            jumble............................ 050516, ref SDS 98 DM77
CA0461 -  ..
CA0462 - SDS subject index theory and practice was reviewed recently on 071010.
CA0463 - ref SDS B7 01DF  At that time, improvements were developed to apply
CA0464 - standardized accounts for "major" subjects.  Standardization and
CA0465 - implementation with software code reduces the time required for
CA0466 - context management. ref SDS B7 569M
CA0468 -  ..
CA0469 - SDS provides chronologies of context that yield the power of knowledge
CA0470 - from "connecting the dots" of cause and effect (see the "locality"
CA0471 - principle in NWO, ref OF 15 I38N).  Root cause analysis aids discovery
CA0472 - of correlations, implications and nuance that makes sense of
CA0473 - complexity, which otherwise overwhelms people in the "fog of war" on
CA0474 - the job day-to-day (see example in medical practice cited in NWO.
CA0475 - ref OF 18 PXWX).  On 040622 Jack Park cited value of "sensemaking" for
CA0476 - learning. ref SDS 94 FM5W  The subject index organizes the record into
CA0477 - lessons learned that enable continual learning on the job, and for
CA0478 - training.
CA0480 -  ..
CA0481 - The SDS subject index takes much longer than indexing a computer for
CA0482 - keywords.  Investing extra time tending the "Garden of Knowledge, as
CA0483 - called out in NWO, ref OF 15 OP6K, complements traditional alphabet
CA0484 - technology for growing deeper understanding that makes sense of
CA0485 - complexity, explained in POIMS. ref OF 9 VK9I  When the computer does
CA0486 - the only indexing, there is no cognitive energy to expand awareness
CA0487 - that small issues reveal major opportunities and solve big problems,
CA0488 - cited by Morris on 921127 as an important requirement for proactive
CA0489 - management. ref SDS 14 0674
CA0490 -
CA0491 -
CA0492 -
CA05 -

SUBJECTS
Diligence Hard Work Paradigm Shift Efficient Usability Makes Working

CC03 -
CC0401 -  ..
CC0402 - Fun Attractive Context Management Efficient Usability Paradigm Shift
CC0403 - Diligence Paradigm Shift Make Working Intelligently Fun Interesting
CC0404 -
CC0405 - Morris makes an important point today that granular indexing of
CC0406 - relational and hierarchial flexible structures required to manage
CC0407 - subjects with multiple views looks tedious and shocking compared to
CC0408 - minimal detail when busy people focus only on the "Big Picture," shown
CC0409 - by example on 890523. ref SDS 2 RC5K  The complexity of relevant
CC0410 - context can be overwhelming, shown further by example on 890523.
CC0411 - ref SDS 2 428F  This assessment aligns with research at SRI on 000307
CC0412 - reporting that Knowledge Management without SDS is a lot of hard work
CC0413 - that takes a lot of diligence.
CC0415 -  ..
CC0416 - Technology with efficient usability, discussed above, ref SDS 0 IF4I,
CC0417 - makes context management for working intelligently fast, easy, and fun
CC0418 - yielding fascinating and critical discoveries that make leadership
CC0419 - effective.  SDS combines accounting principles of alignment and
CC0420 - accuracy, with WBS practices that organize all of the work according
CC0421 - to cause and effect.  This combination strengthens communications,
CC0422 - explained in NWO citing the "locality principle" for intelligence
CC0423 - support. ref OF 15 P69F  On 950303 Morris developed a graphic showing
CC0424 - how aligning communications keeps work on target. ref SDS 19 3497
CC0426 -  ..
CC0427 - Accordingly, SDS changes the paradigm from "diligence" to having fun
CC0428 - like playing a piano makes both hands an instrument of mental melodies
CC0429 - constructing a harmonious symphony, explained in POIMS. ref OF 9 6M5H
CC0430 -
CC0431 -     [On 080104 Morris and Jack discuss Rod applying diligence to do
CC0432 -     Knowledge Management with Microsoft programs, and tools like Iris,
CC0433 -     and does not need SDS even though nobody else is doing it.
CC0434 -     ref SDS C9 OM7N
CC0436 -      ..
CC0437 -     [On 080206 Morris having fun using Ruby on Rails (ROR) Java
CC0438 -     software development technology; makes hard work experimenting to
CC0439 -     test out ideas fast and easy, which reduces the level of diligence
CC0440 -     needed to get things done. ref SDS D3 RR3F
CC0442 -  ..
CC0443 - Jack Park's progress on Topic Maps may be helpful, reported in his
CC0444 - letter on 071113. ref SDS C0 VY7X  Experiencing tedium for subject
CC0445 - indexing may help people discover better paths for technology to
CC0446 - leverage innate intelligence.
CC0448 -  ..
CC0449 - As well, "discovery" from "tedium" using SDS to track and organize the
CC0450 - record helps make sense of complexity, noted by Jack Park on 001130.
CC0451 - ref SDS 58 H17O  On 040622 Jack cited benefits of "sensemaking" for
CC0452 - getting things done correctly. ref SDS 94 FM5W  On 011003 Eric
CC0453 - Armstrong complained that finding information piling up on computers
CC0454 - is not effective, because productivity is paralyzed using popular
CC0455 - search tools. ref SDS 68 EC5N  Earlier Eric noted on 010916 amazing
CC0456 - work product using SDS mechanisms that obviously work. ref SDS 66 0001
CC0457 - A few weeks ago on 071126, Kaiser relied on SDS rather than popular
CC0458 - search tools at Kaiser and UCSF to solve a complex problem.
CC0459 - ref SDS C2 TH8L
CC0461 -  ..
CC0462 - Concern that SDS subject index support for context management with
CC0463 - Control Fields is shocking, and overwhelming correlates with feeling
CC0464 - that links in SDS records are beyond reach, reported by Murray Altheim
CC0465 - on 020820. ref SDS 76 6P8K  Dave Snowden, then at IBM made similar
CC0466 - comments a month later on 020920. ref SDS 77 PS6O  The level of detail
CC0467 - managing context with granular indexing to create organic structure in
CC0468 - the Subject Index is hard to accomplish using conventional tools for
CC0469 - Windows applications.  Morris seemed to indicate today that since, as
CC0470 - noted previously on 010924, ref SDS 67 XT5F, nobody is willing to
CC0471 - diligently invest time for organizing the record with tools that make
CC0472 - Knowledge Management a lot of hard work, cited on 000307, ref SDS 41
CC0473 - 767G, then everybody is unwilling to work with SDS tools that make
CC0474 - Knowledge Management fast, easy, and fun saving lives, time, and
CC0475 - money.
CC0477 -  ..
CC0478 - On 020110, Morris indicated SDS support for intelligence to "connect
CC0479 - the dots" understanding cause and effect, e.g., Subject Index, Control
CC0480 - Fields, case studies, which are difficult with other tools, is
CC0481 - unnecessary overkill. ref SDS 71 2W5J  This was discussed previously
CC0482 - on 010720. ref SDS 63 L25K
CC0484 -  ..
CC0485 - Morris discussed on 020110 that Rod could apply more diligence and use
CC0486 - Microsoft products to accomplish SDS functionality. ref SDS 71 5HYX
CC0487 - and ref SDS 71 T354
CC0489 -  ..
CC0490 - On 001126 Eugene Kim advocated greater diligence using Microsoft
CC0491 - programs everybody likes for Knowledge Management rather than use SDS.
CC0492 - ref SDS 56 4E3X  Eugene did excellent work providing a website portal
CC0493 - on the Internet for people to implment recommendations to use greater
CC0494 - diligence.  There is no evidence anyone else ever applied enough
CC0495 - diligence to accomplish any aspect of SDS.  On 070904 there was a
CC0496 - report that everybody gave up. ref SDS B2 DV5R
CC0498 -  ..
CC0499 - Gary Johnson reported on 040227 that experience at Boeing using
CC0500 - Microsoft programs with greater diligence was unsuccessful
CC0501 - accomplishing SDS support for intelligence. ref SDS 87 RH6K  On 040402
CC0502 - Gary reported in a letter to the Aerospace Company that SDS was
CC0503 - approved for use "good-to-go") again, ref SDS 90 LN7T, and advised
CC0504 - that notes taken with Microsoft Word and Outlook documents for the
CC0505 - prior 2 months are being entered into SDS for command and control of
CC0506 - the record. ref SDS 90 GO6U  On 040404 Gary's letter to Morris
CC0507 - explained efforts to capture the record of organizational memory using
CC0508 - greater diligence applying Microsoft tools without SDS. ref SDS 91
CC0509 - 0K3O
CC0511 -  ..
CC0512 - Worry about complexity and diligence for effective context management
CC0513 - has caused people to give up organizing the record, shown recently on
CC0514 - 071113.  At that time, Jack Park submitted a paper, "Technology of
CC0515 - Cooperation," listing popular tools and practices for Knowledge
CC0516 - Management.  It contains a single mention of "metadata," a term
CC0517 - describing context management efforts in mainstream technology.
CC0518 - ref SDS C0 NQ8J  Case study on 070126 shows everybody has given up on
CC0519 - context management, linking, and capturing the record... all three
CC0520 - elements of Knowledge Management, ref SDS A3 QH8L, which have been
CC0521 - recognized as essential for paperless office efficiencies of
CC0522 - electronic records management, identified by Vannevar Bush in an
CC0523 - article published in 1945, reviewed on 960304. ref SDS 23 GX59
CC0525 -  ..
CC0526 - On 970116 Morris asked about organizing the work with "fractionalized
CC0527 - subjects," indicating awareness that context management is a lot of
CC0528 - hard work using conventional tools. ref SDS 28 1732  On 980405 he
CC0529 - noted again that context management is too difficult for executives,
CC0530 - managers, engineers, and everybody, using tools and practices commonly
CC0531 - available. ref SDS 30 2532  Hard work performing context management
CC0532 - with subject indexing was reported in an article published in Byte
CC0533 - magazine, reviewed on 910418. ref SDS 8 5584  Perhaps the most
CC0534 - shocking aspect of SDS is the new way of working that changes from
CC0535 - organizing documents to assign subjects at the paragraph level, or, as
CC0536 - applied in SDS, to the record segment.
CC0538 -  ..
CC0539 - Continuing aversion against records management enabled by SDS at the
CC0540 - paragraph level (actually record segment) with granular subject
CC0541 - indexing aligns with case study on 070126 showing people have given up
CC0542 - trying to organize the record. ref SDS A3 WV5K  Shock, frustration and
CC0543 - disillusionment with complex DNA-like indexing to control lower levels
CC0544 - of organic structure, i.e., command and control of the "microcosm"
CC0545 - discussed at Intel on 950927, ref SDS 21 5412, is matched by giving up
CC0546 - on linking, reported on 020820, ref SDS A3 YV4F, citing earlier study
CC0547 - on 020812. ref SDS 75 659F  In order to make linking a routine part of
CC0548 - augmenting intelligence, subjects must be assigned below the level of
CC0549 - documents.
CC0551 -  ..
CC0552 - Scope of tools for command and control of "fractionalized" subjects,
CC0553 - was explained on 890523. ref SDS 2 T15F
CC0555 -  ..
CC0556 - As seen today, without effective tools, observing the microcosm of
CC0557 - details arising routinely in daily life, further illustrated by the
CC0558 - example on 890523, ref SDS 2 G14K, overwhelms conscious mental
CC0559 - processing, because mind-numbing complexity is normally supressed by
CC0560 - subconscious processing, explained in POIMS. ref OF 7 8774  After
CC0561 - meeting for an hour or so, most people when asked what was discussed
CC0562 - will remember only 2 or 3 subjects, at most 7, based on cognitive
CC0563 - research reported by Professor Miller in his famous 1955 essay, and
CC0564 - reviewed on 990303. ref SDS 34 5328
CC0566 -  ..
CC0567 - Failure of technology to enable effective metadata and links reflects
CC0568 - negative synergy between failure to organize the record, and failure
CC0569 - to construct connections for accurate understandings, see traceability
CC0570 - to original sources reviewed on 950721. ref SDS 20 1740  Negative
CC0571 - synergy from failure to perform subject indexing leads to everything
CC0572 - being filed miscellaneous, reviewed in a book cited by Jack Park on
CC0573 - 070729. ref SDS A9 HE6N  This causes management productivity to
CC0574 - implode toward entropy, reported by USAFIT study reviewed on 970707.
CC0575 - ref SDS 29 0108
CC0577 -  ..
CC0578 - Similarly, support for chronology, context, and connection explained
CC0579 - in POIMS, ref OF 9 8555, yields positive synergy that grows an
CC0580 - expanding garden of knowledge in the subject index, observed by Morris
CC0581 - today, ref SDS 0 ZJ3H, and a rich harvest of connections in SDS
CC0582 - records like this one that increase the power of knowledge under the
CC0583 - locality principle, reviewed on 040312. ref SDS 88 YH4G  Locality is
CC0584 - also presented in NWO. ref OF 15 I38N  On 010916 Eric Armstrong noted
CC0585 - that SDS mechanisms are obviously effective finding details in time to
CC0586 - be effective. ref SDS 66 0001
CC0588 -  ..
CC0589 - We did not have time today for demonstrating tools and processes that
CC0590 - construct and manage 3-parts comprising the organic structure of
CC0591 - context, described recently on 071010. ref SDS B7 01DF  Earlier, this
CC0592 - was improved on 070511, ref SDS A4 0001, shortening the time required
CC0593 - to construct and assign subjects. ref SDS A4 DA8J  Evaluation at that
CC0594 - time indicated significant improvement. ref SDS A4 1541  Follow up
CC0595 - work on 071010 made corrections, ref SDS B7 GE46, and refined the code
CC0596 - to apply primary and subaccounts that help resolve Morris' concern
CC0597 - today about people getting tired and giving up doing Context
CC0598 - Management. ref SDS B7 1573  SDS technology strives to reduce the
CC0599 - level of effort and make the work fun rather than a test of diligence.
CC0600 -
CC0601 -
CC0602 -
CC0603 -
CC0604 -
CC07 -

SUBJECTS
Save Lives Time Money Case Study Examples SDS Application Self-evide

CM03 -
CM0401 -  ..
CM0402 - Save Lives Time Money Examples SDS Application
CM0403 - Examples SDS Application Save Lives Time Money
CM0404 -
CM0405 - Morris asked for examples using SDS to save lives, time, and money...
CM0407 -         ..
CM0408 -    1.  Morris has 20 years experience with SDS records.  He tried
CM0409 -        using SDS on 910520, and seemed at that time to save time and
CM0410 -        money the first day. ref SDS 9 655O  At that time, Morris
CM0411 -        commented on how fast SDS performs routine tasks. ref SDS 9
CM0412 -        HV51  Responsiveness and efficient SDS usability was noted
CM0413 -        later by Mike Poremba on 020531. ref SDS 72 5M3G
CM0415 -         ..
CM0416 -    2.  Morris' experience saving time and money working intelligently
CM0417 -        on one day was replicated and noted by USACE in a report
CM0418 -        published on 971007. ref DRP 6 0001  An example of common
CM0419 -        problems solved by SDS that saves time and money was RFP #19
CM0420 -        considered in the San Francisco District on 961208. ref SDS 28
CM0421 -        0006
CM0423 -         ..
CM0424 -    3.  PG&E reported improved earnings using SDS for Communication
CM0425 -        Metrics on 951110. ref SDS 16 0001
CM0427 -         ..
CM0428 -    4.  Vice President Dutra Engineering reported SDS record saved time
CM0429 -        and money on Oakland Harbor project. ref SDS 27 4953
CM0431 -         ..
CM0432 -    5.  USACE report cost savings using SDS for Communication Metrics,
CM0433 -        received 971007, ref DRP 6 0001, citing ROI 10:1. ref DRP 6
CM0434 -        7401
CM0436 -         ..
CM0437 -    6.  USACE counsel later wrote a letter on 981027 citing additional
CM0438 -        savings that continued to accrue long after SDS was no longer
CM0439 -        used at the agency. ref SDS 33 7315
CM0441 -         ..
CM0442 -    7.  Broadwater Dam case study on 990316 identified cost saving
CM0443 -        factors. ref SDS 35 4752
CM0445 -         ..
CM0446 -    8.  DNRC reported on 010725 SDS saved time and money on Broadwater
CM0447 -        Dam. ref SDS 64 KH5W
CM0449 -         ..
CM0450 -    9.  Last week, Millie received notice in a letter that Kaiser will
CM0451 -        pay $10K - $20K per year for life saving treatment on referral
CM0452 -        at UCSF.  SDS records on patient history led Kaiser to withdraw
CM0453 -        30 notices over the past year demanding Millie pay, and UCSF
CM0454 -        sent letters threatening termination of care and collection
CM0455 -        actions, reported on 071031. ref SDS B8 KM4J  Kaiser previously
CM0456 -        relied on terms in the insurance policy that say patients must
CM0457 -        pay for treatment at issue, reported on 071206. ref SDS C4 TH8L
CM0458 -        SDS records over the past 6 years show the context in this case
CM0459 -        justifies payment by Kaiser.
CM0461 -         ..
CM0462 -   10.  Several weeks ago, Kaiser's representative explained that
CM0463 -        finding critical details in SDS, ref SDS C1 NE7V, is faster and
CM0464 -        easier than using records from Kaiser and UCSF computers.
CM0465 -        ref SDS C1 NE5P
CM0467 -         ..
CM0468 -   11.  Examples of "life saving" scenarios are continous, illustrated
CM0469 -        by NWO. ref OF 18 PXWX, and based on actual events reported in
CM0470 -        the record on 041230. ref SDS 97 XQ84
CM0472 -         ..
CM0473 -   12.  Primary care physician, chief of Oncology for Kaiser Diablo
CM0474 -        Service Area, advised patient lived 3 times longer than normal
CM0475 -        for cancer disease trajectory because patient has support for
CM0476 -        case management than other patients don't have, reported on
CM0477 -        090213. ref SDS D7 NY7L
CM0478 -
CM0479 -
CM0480 -
CM0481 -
CM0482 -
CM0483 -
CM0484 -
CM05 -

SUBJECTS
Planning Follow Up SDS Windows Application Vision Develop Test Code

CW03 -
CW0401 -  ..
CW0402 - Follow Up Planning and Opportunities Review in about 6 Weeks
CW0403 -
CW0404 - Follow up ref SDS C0 JR97, ref SDS B9 JR97.
CW0405 -
CW0406 - Morris will work on the code the next 3 - 4 weeks to experiment
CW0407 - testing his vision for an alternative to line numbers that enable
CW0408 - efficient usability with flexible structure endimic to SDS records and
CW0409 - Contact records, per above. ref SDS 0 ST3J
CW0411 -  ..
CW0412 - He will try to get some code that will produce program screens that
CW0413 - can be reviewed in meeting sometime in mid-to-late January 2008, say
CW0414 - 4 - 6 weeks.
CW0416 -  ..
CW0417 - After we meet to review progress, Morris will then write up an
CW0418 - explanation of goals, elements, and sequence for implementing the
CW0419 - vision, implementing planning on 070907. ref SDS B3 JR97
CW0420 -
CW0421 -        [On 080124 a lot of time invested to formulate interesting and
CW0422 -        imaginative narrative demonstrating work product of initial SDS
CW0423 -        design for Windows application by paradoying use of numbers for
CW0424 -        managing interesting and imaginative narrative; same effort
CW0425 -        would be more productive writing up explanation of goals and
CW0426 -        specifications for SDS. ref SDS D0 FW4J
CW0427 -
CW0428 -
CW0429 -
CW0430 -
CW0431 -
CW0432 -
CW0433 -
CW05 -