440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700


DIARY: November 13, 2007 07:00 AM Tuesday; Rod Welch

Visit Morris to develop Windows version SDS Contacts.

2...Review Prior Meeting for Common Understandings Not Performed
....1...Version Control Record Integrity Lock Down
........Deliberative Analysis Reduce Mistakes Increase Innovation
........Refine Accuracy Expand Span of Attention over Days Weeks Months
3...Experience with Contacts Software Aids Starting Work on SDS Program
4...Contacts Initial Design Development Effort SDS Windows Version
5...Design SDS Contacts Aided by Experience Using Other Contact Software
6...Progress on Contacts Overcome Difficulties Understanding Knowledge Management
7...Data Structures Contacts System 2 Primary Data Bases
....3...Open Source Contact Management
........Customer Relations Management Contacts Software Programs
........Simple Solutions Scarce
........Contacts Not Place Start SDS Windows Application Design
........XML Editor Editor Data Storage Complicates SDS Application
........Open Source Editors Situation Is Similar
8...Efficient Usability Responsive DOS Editor Structured Analysis
9...XML Case Study Knowledge Management Application
10...Case Study XML Application for Knowledge Management
....2...Contacts Data Structures Granular Addressability
........Documents Add References Similar to SDS Records
....6...Add URLs as a Reference Type
11...Engelbart and Nelson Used References to Link Documents in 1960s
12...Contacts User ID Add to Data Structure
13...User ID Add to Contacts Data Structure
....9...Individuals Within Company Organization Contact Record
........Organization Reference Link Personal Contact Record for Details
........Recursive Contacts Organization Department Reference Individual
...11...Templates For Parts of Contacts Record
........Personnel File Derived from Personal Contact Records
........Integrate Personal Organizational Contacts into 1 Data Base
........Gary Comments on Relationship Between Companies and Individuals
14...Sensemaking Topic Maps Dialog Issues Analysis
15...Topic Maps Lesson Everything Connected Everything Else
16...Contacts Primary Subject Everything Connected Everything Else
17...Everything Connected Everything Else Contacts Base Subject Identifier
........Technologies of Cooperation
18...Printing Press Extended Power Alphabet Amplify Power of Thinking
19...Alphabet Technology Improved with Technology to Lift Civilization
20...Cooperation Networks Knowledge Management for Social Collectives
21...Networks Enable Cooperation Social Collectives Knowledge Management
22...Things We Don't Talk About Around Hear SDS POIMS NWO
23...Knowledge Management Intelligence Communication Metrics Support Missing
24...Chronology Context Connection Complement Technologies of Cooperation
25...Complementarity Leverages Technologies of Cooperation with POIMS
26...Everything Connected Makes Everything in Right Place Right Time
27...Collaboration Helpful Transformation to Culture of Knowledge
28...Meeting Schedule Collaborate Knowledge Management SDS Development
29...Knowledge Management Collaboration Meeting Communicating Contributing
30...Java XML Technology Iris Not Far from SDS
31...Iris Not Far from SDS Jack Contributing for Fun
32...Fun Contributing SDS Work Java Developing IRIS Needs Work Product
33...Work Product Missing Knowledge Management Technologies Except SDS
34...SDS Hope Success Without Meeting Helping Goal for Many
35...Busy No Time Meet Deliberate Collaborate on Advancing Civilization
36...Everything Subject Pointer Topic Map Data Base Unique Locators
37...Personnel File Part Personal Contacts Stable Data
38...Jack Comments 1 Data Base Personal Organizational Contacts Data Base
39...Contacts Integrate Personal Organizational into One Data Base
40...Transferrability Contacts Between Individual to Organization
41...Contacts Screens Pending Revisions and Expand Code from Review Today
42...Follow Up Planning and Opportunities

ACTION ITEMS.................. Click here to comment!

1...Not sure, but seemed like result today was to make SDS Contacts a
2...Not sure what Gary has in mind here, need clarification, example.


SDS Windows Application Review Design Scope Requirements Version Con

1303 -
1303 -    ..
1304 - Summary/Objective
1305 -
130501 - Follow up ref SDS A6 0000. ref SDS A2 0000.
130502 -
130503 - Reviewed background from prior work. ref SDS 0 V35O  Morris submitted
130504 - some code he has developed toward creating initial screens and
130505 - functionality, now planned for review in 2 weeks. ref SDS 0 O65H  Gary
130506 - submitted comments on Contacts data structures. ref SDS 0 4T67  Morris
130507 - explained multi-user Contacts system, ref SDS 0 6I4N, discussion
130508 - centered on starting with a single-user design that maintains
130509 - responsiveness. ref SDS 0 U95K  Jack Park suggests using code from
130510 - open source work, and cites progress with Iris, based on Java
130511 - technology. ref SDS 0 VY7X  Gary supports open standards where
130512 - possible.  Morris discussed XML editing for the new version of SDS.
130513 - ref SDS 0 445I  A case study shows many efforts to develop Knowledge
130514 - Management tools using XML have failed to balance speed and structure,
130515 - with benefits of professional appearance. ref SDS 0 XC3M  Gary noted
130516 - during the call today that XML presents issues of slow responsiveness,
130517 - ref SDS 0 LY7W, which aligns with research on Iris, citing risks from
130518 - "denial of service" attacks. ref SDS 0 IU9L  SDS responsiveness turns
130519 - computer technology into an "intelligence" asset for structured
130520 - analysis based on situational awareness and so must be retained.
130521 - ref SDS 0 EF8M  Jack reports that talking about SDS development is
130522 - fun, ref SDS 0 U86H; using SDS to save lives, time, and money can also
130523 - be fun with everything in the right place at the right time.  Using
130524 - left and right brain power to apply complementary tasks makes the
130525 - structure of knowledge for working intelligently fun, like playing a
130526 - piano. ref SDS 0 CU6I
130527 -
130528 -     [On 071210 letter submitted record of meeting, and confirms
130529 -     schedule next meeting. ref SDS A9 7V7K
130530 -
130531 -
130533 -  ..
1306 -
1307 -
1308 - Background
1309 -
130901 - Review Prior Meeting for Common Understandings Not Performed
130902 -
130903 - Follow up ref SDS A6 V35O, ref SDS A2 V35O.
130904 -
130905 - Morris has received correspondence between Jack and Gary collaborating
130906 - on ideas for SDS, listed on 070914, ref SDS A4 QC5H, and cited during
130907 - the meeting last week on 071106. ref SDS A6 5Q3K
130909 -  ..
130910 - Subsequent correspondence reviewed during the meeting includes...
130911 -
130912 -    1.  Gary letter to Jack on using open source
130913 -        tools and standards........................... ref SDS 0 2J8H
130914 -
130915 -    2.  Gary letter to Morris on expanding SDS
130916 -        record support for granular addressability
130917 -        to Contact records............................ ref SDS 0 4S81
130919 -         ..
130920 -    3.  Jack letter to Gary advises SDS design
130921 -        described by Gary seems similar to
130922 -        early work by Engelbart and Nelson
130923 -        in 1960s...................................... ref SDS 0 4S68
130925 -         ..
130926 -    4.  Gary letter to Morris comments on proposed
130927 -        Contacts data structures...................... ref SDS 0 4T67
130929 -         ..
130930 -    5.  Jack letter to Gary explains topic maps
130931 -        relate everything to everything
130932 -        else.......................................... ref SDS 0 IV5F
130934 -         ..
130935 -    6.  Letter to Jack reports background applying
130936 -        concept of multiple-cross-referencing
130937 -        for creating a connected
130938 -        record........................................ ref SDS 0 ZJ3H
130940 -         ..
130941 -    7.  Letter Jack reports he cannot meet to
130942 -        collaborate too busy with other
130943 -        matters....................................... ref SDS 0 QV9O
130945 -         ..
130946 -    8.  Letter Jack comments on using topic maps
130947 -        for context management........................ ref SDS 0 M14K
130949 -  ..
130950 - We went for a walk 2 - 3 miles again this morning and continued
130951 - discussion on 071106 about contacts. ref SDS A6 FL3F
130952 -
130953 -    1.  Prior meeting on...
130954 -
130955 -               070907........................... ref SDS A2 0001
130956 -               071106........................... ref SDS A6 0001
130958 -         ..
130959 -    2.  Reviewed contacts data structures in the record on 071106.
130960 -        ref SDS A6 0R4H
130962 -         ..
130963 -        See discussion below. ref SDS 0 O65H
130964 -
130965 -
130966 -
130967 -
130968 -
1310 -

Document Management Version Control Multi-user System Software Data

4003 -
4004 - Progress
400501 -         ..
400502 -    1.  Version Control Record Integrity Lock Down
400503 -        Deliberative Analysis Reduce Mistakes Increase Innovation
400504 -        Refine Accuracy Expand Span of Attention over Days Weeks Months
400505 -
400506 -        Follow up ref SDS A6 6I4N.
400507 -
400508 - Morris explained "lock down" features are required for multi-user
400509 - systems.  This seems to arise in three common use cases...
400510 -
400511 -        a.  People attempting to access the same document at the same
400512 -            time.
400514 -  ..
400515 - Discussion today indicated a solution of individuals saving records
400516 - under their own user ID, similar to subjects.  Formal document
400517 - management practices include version control, and lock down.
400518 -
400519 -        b.  Links into documents failing because editing removes
400520 -            anchors.
400522 -  ..
400523 - Morris seemed to indicate that volitality of links on the Internet
400524 - arising in part from people removing documents, and simply closing a
400525 - web address is replicated using SDS records.  There was also concern
400526 - that experience using SDS the past 20 years has not entailed cross
400527 - referencing records between multiple users.
400529 -  ..
400530 - Discussion this moring cited examples of recent letters Gary sent to
400531 - Morris and others linked to Rod's SDS records, e.g., on 071112, and
400532 - earlier on 070913.  Another example is the record on 070907,
400533 - ref SDS A2 645L, citing Gary's SDS record on 070823. ref SDS 99 J04M
400535 -  ..
400536 - Links in SDS occassionally get "broken" but this has not been a big
400537 - enough problem to require "lock down."
400539 -             ..
400540 -        c.  Integrity of the record for litigation support, e.g., court
400541 -            testimony.
400543 -  ..
400544 - This was reviewed last week on 071106. ref SDS A6 6I4N
400546 -  ..
400547 - Decided not to provide version control and lock down common to
400548 - multi-user systems, explained further below. ref SDS 0 MH9T
400549 -
400550 -
400551 -
400552 -
400553 -
400554 -
4006 -

Contacts Experience Microsoft Outlook Netscape Mozilla Thunderbird O

7103 -
710401 -  ..
710402 - Experience with Contacts Software Aids Starting Work on SDS Program
710403 - Contacts Initial Design Development Effort SDS Windows Version
710404 - Design SDS Contacts Aided by Experience Using Other Contact Software
710405 - Progress on Contacts Overcome Difficulties Understanding Knowledge Management
710406 -
710407 - Follow up ref SDS A6 W889.
710408 -
710409 - Work on 070907, ref SDS A2 JQ88, and again on 071106, ref SDS A6 W889,
710410 - shows collaboration to advance from information to knowledge tools is
710411 - difficult, ref SDS A6 OS6M, similar to contentious debates with
710412 - invention of the transistor at Bell Labs in the 1940s, reported on
710413 - 960304, ref OF 20 8D4N, and citing requirements to rely on SDS design
710414 - that has invented an effective "wheel" for converting information into
710415 - the power of knowledge, noted on 071106. ref SDS A6 UJ8N
710417 -  ..
710418 - Decided to start development of Contacts for designing a new version
710419 - of SDS, ref SDS A6 FL3F, based on case study of prior work developing
710420 - this feature. ref SDS A6 WL8F
710421 -
710423 -  ..
710424 - Data Structures Contacts System 2 Primary Data Bases
710425 -
710426 - Follow up ref SDS A6 2J8H.
710427 -
710428 - Received letter from Gary at Boeing dated 071112 with copy to Jack and
710429 - Morris, commenting on the record meeting last week on 071106, and
710430 - saying...
710431 -
710432 -    1.  Subject:  Meeting with Morris on SDS Contacts Design
710433 -        Date: Mon, 12 Nov 2007 08:13:35 -0800
710438 -         ..
710439 -    2.  Jack,
710441 -         ..
710442 -    3.  Open Source Contact Management
710443 -
710444 -    4.  I am definitely in favor of open source when I can find it.
710446 -         ..
710447 -    5.  A really quick look turns up lots of "well-oiled" contact
710448 -        managers that are open source.
710449 -
710451 -         ..
710452 -        Customer Relations Management Contacts Software Programs
710453 -
710454 -    6.  The majority of them are Customer Relationship Management (CRM)
710455 -        applications. These tend to be web-based and oriented toward
710456 -        sales and marketing, including contact sharing.  Most are
710457 -        either Java or PHP applications.  Morris thinks in C++ Terms.
710459 -         ..
710460 -    7.  They have far more features than SDS needs or wants.
710462 -         ..
710463 -    8.  There are fewer contact database solutions, but they are
710464 -        generally simple database apps over MySQL or similar.
710466 -         ..
710467 -    9.  Any / All are grist for the mill for database structures,
710468 -        however.
710470 -         ..
710471 -   10.  What would be nice are interfaces to Outlook and Thunderbird.
710472 -        Where these exist for open source CRM solutions, they seem to
710473 -        be proprietary.
710474 -
710476 -         ..
710477 -        Simple Solutions Scarce
710478 -        Contacts Not Place Start SDS Windows Application Design
710479 -
710480 -   11.  I don't think that the Contacts system is the place to start
710481 -        with SDS, but I am not doing the code, so I get a voice, not a
710482 -        vote.
710483 -
710484 -            [On 080206 Morris proposed using a generic Contacts system
710485 -            rather than create support to make SDS effective for daily
710486 -            management. ref SDS B8 C77K
710488 -         ..
710489 -   12.  I find it interesting that here, as in many other areas, that
710490 -        as the overall sophistication increases the availability of
710491 -        simple(r) solutions dwindles.  If you want to manage the entire
710492 -        customer acquisition and relationship development cycle, there
710493 -        are any number of solutions.  If you want to manage personal
710494 -        contacts there is hardly anything between email address books
710495 -        and the CRM applications.  Solutions are web-based and
710496 -        enterprise level.
710498 -         ..
710499 -   13.  I find that a bit interesting as it seems that the individual
710500 -        developer has become an anachronism, and the small team is not
710501 -        well supported, and yet there are huge numbers of small teams
710502 -        that can use support.  Most open source projects qualify as
710503 -        small team projects in fact.
710504 -
710505 -
710506 -
710507 -
7106 -

Open Source Editors Not Available for SDS Requirements Scintilla Eng

AO03 -
AO0401 -         ..
AO0402 -        XML Editor Editor Data Storage Complicates SDS Application
AO0403 -        Open Source Editors Situation Is Similar
AO0404 -
AO0406 -  ..
AO0407 - Gary's letter dated 071112 continues...
AO0408 -
AO0409 -   14.  When I went looking for open source editing solutions, nearly
AO0410 -        all the text editors provide syntax highlighting and many other
AO0411 -        features that get in my way.  Many use the Scintilla engine as
AO0412 -        a base.  Move to rich text and the results leap to nearly
AO0413 -        word-processing sophistication.
AO0415 -         ..
AO0416 -   15.  Add to that the shift to Java over the last several years, and
AO0417 -        the pickings are very slim. (Apart from not wanting to tackle
AO0418 -        the enormous infrastructure that is Java, the Java-based
AO0419 -        editors I have seen tend to be sluggish.)
AO0421 -  ..
AO0422 - On 000331 Jack Park discussed XML editor considerations on OHS/DKR
AO0423 - project discussed at SRI. ref SDS 39 TQ52  He used an XML editor to
AO0424 - develop a software program called "Scholar's Companion," reported on
AO0425 - 000324. ref SDS 37 3816
AO0427 -  ..
AO0428 - On 021214 Gary cited slow responsiveness of Java for XML web
AO0429 - applications, ref SDS 79 LN5G; slow performance was observed on 060211
AO0430 - testing Iris, which is part of the CALO project at SRI sponsored by
AO0431 - DARPA, ref SDS 90 055L  Slow response of Java-XML was cited in a case
AO0432 - study at that time on 060211. ref SDS 90 OZ31
AO0434 -  ..
AO0435 - Jack confirms in a letter today that Iris is an open source, Java
AO0436 - Internet application; he feels Iris supports SDS requirements.
AO0437 - ref SDS 0 VY7X
AO0438 -
AO0439 -        [On 080104 Morris considering Java Data Object programming
AO0440 -        for SDS Windows application. ref SDS B4 8O5H
AO0442 -         ..
AO0443 -        [On 100928 1348 testing Medit Java indicates very slow
AO0444 -        performance with Java on Windows XP, and much slower on
AO0445 -        Windows 7 64-bit. ref SDS B9 RJ4O
AO0447 -  ..
AO0448 - In the conference call with Gary this morning, there was discussion of
AO0449 - editing support.
AO0451 -  ..
AO0452 - Morris seemed to mention this morning that an XML editor would be
AO0453 - effective for the new Windows version of SDS.
AO0454 -
AO0456 -  ..
AO0457 - Efficient Usability Responsive DOS Editor Structured Analysis
AO0458 -
AO0459 - DOS-based editor makes structured analysis fast and easy required for
AO0460 - management, cited by Morris on 951228, ref SDS 19 S47O, and noted
AO0461 - again on 980405. ref SDS 24 2156  SDS design requirements for flexible
AO0462 - structure were reviewed on 070907, ref SDS A2 FB7H, and again last
AO0463 - week on 071106, ref SDS A6 FL50, and citing prior analysis on 890523.
AO0464 - ref SDS 1 P13O
AO0465 -
AO0466 -            [On 080124 Morris submits work product for new version of
AO0467 -            SDS that omits flexible structure, including line numbers.
AO0468 -            ref SDS B5 H19U
AO0470 -  ..
AO0471 - On 001130 Jack reported that SDS has right the design to represent
AO0472 - knowledge structures, and the user interface makes the structure of
AO0473 - knowledge useful to people. ref SDS 58 H17O  On 010924 Morris
AO0474 - commented that SDS improves management better than other tools,
AO0475 - ref SDS 66 NK4J, because nobody uses software like SDS for capturing
AO0476 - and organizing the record of daily events, ref SDS 66 XT5F, to work
AO0477 - intelligently, as set out in POIMS. ref OF 9 1X6G  Jeff Conklin made a
AO0478 - similar point on 011105. ref SDS 70 4S6H
AO0480 -  ..
AO0481 - On 020531 Mike Poremba reviewed SDS in relation to a Java outline
AO0482 - program, and found SDS is optimized for efficient usability,
AO0483 - ref SDS 72 5M3G; SDS time management makes sense of complex
AO0484 - information so that links are comprehensible, ref SDS 72 OP7M; and,
AO0485 - SDS responsiveness derived from DOS program code with integrated,
AO0486 - complementary functions enables people to work at the speed of human
AO0487 - thought, which is hard to accomplish with other methods. ref SDS 72
AO0488 - 5W9J
AO0490 -  ..
AO0491 - Earlier on 910520, Morris cited amazing speed of SDS tools that
AO0492 - provide efficient usability. ref SDS 8 HV51
AO0494 -  ..
AO0495 - Gary previously noted on 041111 loss of efficient usability creating a
AO0496 - Windows application made Maxthink less productive. ref SDS 88 QQ3K
AO0497 -
AO0498 -    [On 071210 letter to Morris, copy to Gary and Jack cites SDS
AO0499 -    responsiveness makes Knowledge Management fast and easy.
AO0500 -    ref SDS A9 W23Y
AO0502 -     ..
AO0503 -    [On 071219 Gary cites Maxthink and Wordperfect illustrate problems
AO0504 -    engineers encountered that caused loss of efficient usability for
AO0505 -    Windows applications. ref SDS B1 X16G
AO0507 -  ..
AO0508 - Reasons for difficulty evolving Knowledge Management that enables
AO0509 - intelligence support are listed on 010924. ref SDS 66 JS6G   One
AO0510 - factor is lack of responsiveness that competes with mind numbing speed
AO0511 - of relying on "assumption," explained in NWO. ref OF 21 FU6J
AO0513 -     ..
AO0514 -    [On 071212 Morris feels dififculties others have encountered trying
AO0515 -    to use XML can be solved by the design he plans for SDS Wiindows
AO0516 -    application. ref SDS B0 OO3L
AO0518 -     ..
AO0519 -    [On 071222 Morris letter discusses using function keys for
AO0520 -    efficient usability, ref SDS B3 PX5H, shown by requirements for
AO0521 -    responsiveness reviewed at that time. ref SDS B3 FO94
AO0523 -     ..
AO0524 -    [On 080104 Morris considering Java Data Object programming
AO0525 -    for SDS Windows application. ref SDS B4 8O5H
AO0527 -  ..
AO0528 - Gary noted in a recent letter on 070904 that context management takes
AO0529 - too much time for many people to exercise diligence required for
AO0530 - creating a record that enables finding sources to apply granular
AO0531 - addressability which makes verifying accuracy fast and easy.
AO0532 - ref SDS A1 DV7P  SDS responsiveness noted by Mike Poremba, cited
AO0533 - above, ref SDS 0 V45N, solves the problem of filing "everything under
AO0534 - miscellaneous," discussed in a book suggested by Jack Park, reviewed
AO0535 - on 070729. ref SDS 98 HE6N  Faster tools make good management fast,
AO0536 - easy, fun, and effective, also noted on 070729, ref SDS 98 ML6O, to
AO0537 - overcome risks of assumption, but can never eliminate requirements for
AO0538 - diligence to invest time for working intelligently (see again POIMS,
AO0539 - ref OF 10 1X6G, since doing nothing is always faster than doing
AO0540 - anything, noted on 070831. ref SDS A0 1J9U
AO0541 -
AO0542 -    [On 071210 letter to Morris, copy to Gary and Jack cites SDS
AO0543 -    responsiveness makes Knowledge Management fast and easy.
AO0544 -    ref SDS A9 W23Y
AO0546 -  ..
AO0547 - Today, Gary discussed using an ascii text editor, like Medit, and
AO0548 - converting work product into HTML or XML for display in a web browser
AO0549 - when needed.
AO0551 -  ..
AO0552 - Morris noted that work product created in XML format would also
AO0553 - display in a text editor.
AO0554 -
AO0556 -  ..
AO0557 - XML Case Study Knowledge Management Application
AO0558 - Case Study XML Application for Knowledge Management
AO0559 -
AO0560 - Balancing SDS requirements for structure and speed to improve accuracy
AO0561 - against benefits of appearance has been considered previously with
AO0562 - respect to XML technology solutions for Knowledge Management...
AO0563 -
AO0564 -        1.  XML method for structuring data in a file from different
AO0565 -            program formats, e.g., spreadsheets, wordprocessing,
AO0566 -            pictures, etc., that provides a common viewing environment
AO0567 -            where comments can be entered to explain what is displayed
AO0568 -            from other programs, reviewed 000125. ref SDS 30 7568
AO0570 -             ..
AO0571 -        2.  Java data objects may be related to XML and structured
AO0572 -            data, also explained on 000125. ref SDS 30 7568
AO0574 -             ..
AO0575 -        3.  XML editor proposed by Eric Armstrong for OHS/DKR project
AO0576 -            to develop Knowledge Management, reviewed 000129.
AO0577 -            ref SDS 31 0957
AO0579 -             ..
AO0580 -        4.  XML supports collapsable hierarchy to control visible
AO0581 -            presentation that helps grasp structure without detail, and
AO0582 -            obtain detail with clicking a node, reviewed 000129.
AO0583 -            ref SDS 31 PTVQ
AO0585 -             ..
AO0586 -        5.  Java data objects (JDO) research seems to correlate with
AO0587 -            objectives for XML application to Knowledge Management,
AO0588 -            shown on 000129. ref SDS 31 GD6J
AO0590 -             ..
AO0591 -        6.  XML editor development using Java explained in connection
AO0592 -            with masters thesis cited by Jack Park on 000131.
AO0593 -            ref SDS 32 R264
AO0595 -             ..
AO0596 -        7.  Xeena IBM editor XML was propopsed for the OHS/DKR project
AO0597 -            at SRI on 000223 by Eric Armstrong. ref SDS 34 QQ96
AO0599 -             ..
AO0600 -        8.  XML editor programming experience reported by Eric
AO0601 -            Armstrong on 000324, ref SDS 37 FS3J, and also by Jack Park
AO0602 -            who used XML editor for a software project Scholar's
AO0603 -            Companion. ref SDS 37 3816
AO0605 -             ..
AO0606 -        9.  XML editor for Knowledge Management representational issues
AO0607 -            proposed by Jack Park and Adam Cheyer on 000331.
AO0608 -            ref SDS 39 TT40
AO0610 -             ..
AO0611 -       10.  XML was questioned by Paul Fernhout advising the OHS/DKR
AO0612 -            team that knowledge management and representation is a deep
AO0613 -            problem; XML doesn't address it in a serious way, and
AO0614 -            confuses people with hype; Paul feels there is no solution
AO0615 -            to the problem, reported 000405. ref SDS 41 0005
AO0617 -             ..
AO0618 -       11.  XML planned to organize the record in a Dynamic Knowledge
AO0619 -            Repository (DKR), where documents are maintained in
AO0620 -            original form, and commentary is managed separately,
AO0621 -            proposed by Jack Park on 000630. ref SDS 46 MD3O  Jack
AO0622 -            cites SDS records illustrate planned design for knowledge
AO0623 -            repository of document content and separate analysis; Jack
AO0624 -            complains that Welch 1-sided commentary can be improved by
AO0625 -            using XML and IBIS for the DKR. ref SDS 46 RA9I
AO0627 -             ..
AO0628 -       12.  XML editor project for OHS/DKR Knowledge Management
AO0629 -            distributed, versioned, categorized, link-typable, linked,
AO0630 -            node-graph repository, progress reported by Eric Armstrong
AO0631 -            planning release soon on 001017. ref SDS 49 0001
AO0633 -             ..
AO0634 -       13.  Architecture XML editor snag support for linking, Eric
AO0635 -            reports on 001018. ref SDS 51 M4W7
AO0637 -             ..
AO0638 -       14.  XML editor release of code delayed pending resolution of
AO0639 -            design problems on 001106. ref SDS 52 0001
AO0641 -             ..
AO0642 -       15.  XML editor project adandoned Eric disappointed about
AO0643 -            difficulty creating technology support for Knowledge
AO0644 -            Management. ref SDS 54 0001
AO0646 -             ..
AO0647 -       16.  XML limitations for Knowledge Management development
AO0648 -            reviewed by Ken Holman, 001124. ref SDS 55 0001
AO0650 -             ..
AO0651 -       17.  IBM abandoned Raven project to convert Lotus Notes into
AO0652 -            Knowledege Management, nobody could agree on what to
AO0653 -            produce, i.e., what knowledge means, reported 001130.
AO0654 -            ref SDS 57 F26K
AO0656 -             ..
AO0657 -       18.  XML Microsoft project announced expected to yield useful
AO0658 -            tools in 5 years that improve productivity, reported
AO0659 -            010510. ref SDS 63 656F  XML would become the next "killer
AO0660 -            application" in 5 years. ref SDS 63 8Y8H
AO0662 -             ..
AO0663 -       19.  Traction has made progress using XML for Knowledge
AO0664 -            Management applications that has some SDS-like features,
AO0665 -            reviewed on 011102. ref SDS 67 KV6K
AO0667 -             ..
AO0668 -            See example of folks updating the record with Traction.
AO0669 -            ref SDS 67 YT3O
AO0671 -             ..
AO0672 -            Traction work product is described as supporting XML
AO0673 -            technology. ref SDS 67 PO9G
AO0675 -             ..
AO0676 -            Minimal use of chronology, context, and connection in work
AO0677 -            product may indicate limitations of XML and other design
AO0678 -            choices make using Traction not fast and easy.  Lack of
AO0679 -            efficient usablity discourages capturing a greater share of
AO0680 -            daily working information. ref SDS 67 RL8G  This problem
AO0681 -            could have been corrected since 2001.
AO0683 -             ..
AO0684 -       20.  Java case study correlates to work with XML, reported on
AO0685 -            060211. ref SDS 90 YY5K
AO0686 -
AO0687 -
AO0688 -
AO0689 -
AO0690 -
AO0691 -
AO0692 -
AO07 -

Contacts Documents Data Structures References Granular Addressabilit

BE03 -
BE0401 -  ..
BE0402 - Gary submitted another letter adding comment to the meeting on 071106
BE0403 - and pertaining to SDS Contacts data structures...
BE0404 -
BE0405 -    1.  Subject:  Meeting with Morris on SDS Contacts Design
BE0406 -        Date: Mon, 12 Nov 2007 08:23:34 -0800
BE0411 -         ..
BE0412 -    2.  Contacts Data Structures Granular Addressability
BE0413 -
BE0414 -        Follow up ref SDS A6 T56G
BE0416 -         ..
BE0417 -        Looking at this, I want to bring up a point that I have made
BE0418 -        earlier: more of SDS should be based on SDS-like records.
BE0420 -         ..
BE0421 -    3.  SDS records support granular addressability and enable linking
BE0422 -        between key points in any 2 records.  They do this by adding a
BE0423 -        record index at the beginning of the record and using
BE0424 -        references to anchors within those records as hyperlinks within
BE0425 -        the document.
BE0426 -
BE0427 -            [...below Jack reports that work Doug Engelbart did in the
BE0428 -            1960s, and Ted Nelson did separately during that time,
BE0429 -            sounds similar to this part of SDS. ref SDS 0 KA4T
BE0430 -
BE0432 -         ..
BE0433 -        Documents Add References Similar to SDS Records
BE0434 -
BE0435 -    4.  This isn't true, for example, of Other Files, which could
BE0436 -        benefit from a similar index - URL mechanism.
BE0438 -         ..
BE0439 -    5.  It seems that the 2 levels of Contacts could benefit from a
BE0440 -        similar structure, allowing the links between a segment for an
BE0441 -        individual in a company record and the individual's record
BE0442 -        referencing his involvement with that company.
BE0443 -
BE0445 -         ..
BE0446 -    6.  Add URLs as a Reference Type
BE0447 -
BE0448 -        I have also considered adding URLS as a reference type, but
BE0449 -        there is generally only a single reference to a external URL,
BE0450 -        so this isn't nearly so effective as linking between local
BE0451 -        records.
BE0452 -
BE0453 -
BE0454 -
BE05 -

Documents References Links Engelbart Doug and Nelson Ted Used in 196

CF03 -
CF0401 -  ..
CF0402 - Engelbart and Nelson Used References to Link Documents in 1960s
CF0403 -
CF0404 - Jack responded to Gary's explanation of SDS references, and the idea
CF0405 - of adding a field for references in conventional documents, which is
CF0406 - the idea of a biblogrpahy...
CF0407 -
CF0408 -    1.  Subject: Re: Meeting with Morris on SDS Contacts Design
CF0409 -        Date: Mon, 12 Nov 2007 09:04:55 -0800
CF0414 -         ..
CF0415 -    2.  Gary,
CF0417 -         ..
CF0418 -    3.  Your description [in Gary's letter explaining SDS references,
CF0419 -        ref SDS 0 V74W] sounds a lot like what I know about two
CF0420 -        entities:  Ted Nelson's "virtual file" or "virtual document",
CF0421 -        and the file spec in Augment, Doug Engelbart's creation.  An
CF0422 -        Augment file includes an index at the top.  A virtual document
CF0423 -        is just what it says: a file that is purely indexical, with
CF0424 -        start/span numbers (could be URLs with spans added) into
CF0425 -        another space.
CF0427 -         ..
CF0428 -    4.  In Nelson's case, the other space was a continuous character
CF0429 -        string.  Everything you ever type is simply appended to this
CF0430 -        unimaginably long character string, and the virtual document is
CF0431 -        a collection of links into that space.
CF0433 -  ..
CF0434 - Gary Johnson mentioned this type of capability in his letter on
CF0435 - 070831, ref SDS A0 SG4W  Today, Jack provides helpful context with
CF0436 - explanation of capabilities.
CF0438 -  ..
CF0439 - Jack's reference to Nelson's support for linking seems supported by
CF0440 - review of Xanadu on 000305, ref SDS 35 1188; the same review noted
CF0441 - Xanadu tracked version control at a low level of detail, ref SDS 35
CF0442 - 3717, as Jack mentions today.
CF0444 -  ..
CF0445 - Jack's explanation today could be strengthened by indicating if this
CF0446 - is a recollection from seeing the tools being used.  On 000608 Doug
CF0447 - did a demonstration of Augment NLS at SRI for the OHS/DKR team, which
CF0448 - lists "linking" among program features. ref SDS 45 4180
CF0450 -  ..
CF0451 - On 010605 during a meeting at SRI for OHS/DKR which Jack had been
CF0452 - attending, Doug reported doing seminars at SRI on Augment NLS
CF0453 - capabilities. ref SDS 64 9626  On 010329 Jack planned to incorporate
CF0454 - Augment NLS features in a Nexist software program project which Jack
CF0455 - was developing at that time. ref SDS 61 XZ4K
CF0456 -
CF0457 -
CF0458 -
CF0459 -
CF0460 -
CF0461 -
CF05 -

Contacts SDS POIMS Knowledge Management Design User ID Data Structur

D603 -
D60401 -  ..
D60402 - Contacts User ID Add to Data Structure
D60403 - User ID Add to Contacts Data Structure
D60404 -
D60405 - Gary submitted another letter with ideas on data structures listed in
D60406 - the record on 071106. ref SDS A6 T56G
D60407 -
D60408 -    1.  Subject:  SDS Contacts Design Collaboration
D60409 -        Date: Mon, 12 Nov 2007 11:30:57 -0800
D60414 -         ..
D60415 -    2.  Rod,
D60417 -         ..
D60418 -    3.  Looking at the current data structure, here are some thoughts:
D60420 -         ..
D60421 -    4.  Record identification.................. [reported on 071106,
D60422 -        ref SDS A6 0R4H]
D60424 -         ..
D60425 -    5.  In addition to the current info, we had discussed the
D60426 -        possibility of multiple contact lists, with sharing.
D60428 -         ..
D60429 -    6.  Among the possibilities are adding the user id to the record.
D60431 -         ..
D60432 -    7.  Any contacts with a user id would have their record identifiers
D60433 -        managed for that user.  This deconflicts the identifiers when
D60434 -        using contacts as a shared resource.
D60436 -         ..
D60437 -    8.  If we have a use case for a situation where several people need
D60438 -        access to the same set of contacts, we would need to design an
D60439 -        approach.  It might be as simple as taking the record from the
D60440 -        first user to create it and marking it as sharable or as
D60441 -        complex as a shared server for providing new identifiers.
D60443 -  ..
D60444 - Morris discussed this design choice extensively during the hike today,
D60445 - and again during the telephone call with Gary.  Morris and Gary have
D60446 - extensive experience working with large-scale contact systems at Intel
D60447 - and Boeing.  Morris seemed to indicate Microsoft Outlook is used by
D60448 - some organizations to manage contacts.  Evidently there are some
D60449 - issues that have not yet been solved.
D60451 -  ..
D60452 - Contacts multi-user systems require access permissions, lock downs,
D60453 - and delays for many people to use a common data base.
D60455 -  ..
D60456 - Considered advantages of multi-user system design.  Morris explained
D60457 - that manay people benefit from entering changes and corrections made
D60458 - by one person.  This also presents a risk of one person creating
D60459 - mistakes that ripple through everyone's work.
D60461 -  ..
D60462 - Not sure, but seemed like result today was to make SDS Contacts a
D60463 - single user system with the user ID part of the directory structure,
D60464 - similar to the Subject Index, along the lines of Gary's letter, per
D60465 - above. ref SDS 0 MH9X
D60467 -  ..
D60468 - Morris indicated today that a single-user contacts system design that
D60469 - organizes contacts directory structure based on user ID, similar to
D60470 - the Subject Index, simplifies code development.
D60471 -
D60472 -
D60473 -
D60474 -
D605 -

Contacts Data Structures Organization Departments Recursive Links Re

DX03 -
DX0401 -         ..
DX0402 -    9.  Individuals Within Company Organization Contact Record
DX0403 -        Organization Reference Link Personal Contact Record for Details
DX0404 -        Recursive Contacts Organization Department Reference Individual
DX0405 -
DX0406 -        Follow up ref SDS A6 E28P.
DX0407 -
DX0408 -        Here we could consider adding the reference to the individual
DX0409 -        contact record (user id, contact id), usable as a hyperlink.
DX0410 -        Most of the information here seems to be correct for the
DX0411 -        individual within an organization and is therefore proper in
DX0412 -        the company record, down to item 14. ref SDS A6 ID6G
DX0414 -         ..
DX0415 -   10.  That information is stable for the person, rather than for the
DX0416 -        person within the company.  Here might be a good place for the
DX0417 -        link to the individual's contact record.
DX0418 -
DX0420 -         ..
DX0421 -   11.  Templates For Parts of Contacts Record
DX0422 -
DX0423 -        The contact system supports addition of various segment of the
DX0424 -        record such as Departments and Individuals in Departments,
DX0425 -        which is not identified.
DX0426 -
DX0427 - Not sure what Gary has in mind here, need clarification, example.
DX0428 -
DX0430 -         ..
DX0431 -        Personnel File Derived from Personal Contact Records
DX0432 -        Integrate Personal Organizational Contacts into 1 Data Base
DX0433 -        Gary Comments on Relationship Between Companies and Individuals
DX0434 -
DX0435 -   12.  We should look at the possibility of:
DX0437 -             ..
DX0438 -        1.  creating an Individual Contact from the information in a
DX0439 -            Company Contact
DX0441 -             ..
DX0442 -        2.  populating an individual within a Company Contact from the
DX0443 -            information in an Individual Contact
DX0444 -
DX0445 -               [...Rod concurs, citing plans to integrate personal and
DX0446 -               organizational contacts into a single data base, with
DX0447 -               personal contact information forming a "personnel file"
DX0448 -               containting relatively stable data. ref SDS 0 M16R
DX0450 -                ..
DX0451 -               [...below, Jack comments. ref SDS 0 M17R
DX0453 -  ..
DX0454 - During a call with Gary today there was discussion that the new SDS
DX0455 - Contacts system will provide a single contact record format for both
DX0456 - individuals and organizations, and that organization department
DX0457 - structure will reference or otherwise link to appropriate fields for
DX0458 - individuals rather than maintain two data bases.
DX0459 -
DX0460 -
DX0461 -
DX05 -

Topic Maps Lesson Everything Connected Everything Else Contacts Prim

F903 -
F90401 -  ..
F90402 - Sensemaking Topic Maps Dialog Issues Analysis
F90403 - Topic Maps Lesson Everything Connected Everything Else
F90404 - Contacts Primary Subject Everything Connected Everything Else
F90405 -
F90406 - Follow up ref SDS 98 K33H.
F90407 -
F90408 - Jack submitted a 2nd letter today which responded to Gary's
F90409 - explanation of Contact data structures, per above, ref SDS 0 4T67,
F90410 - based on the list in the record for 071106. ref SDS A6 0R4H
F90411 -
F90412 -    1.  Subject:  SDS Contacts Design Collaboration
F90413 -        Date: Mon, 12 Nov 2007 13:09:35 -0800
F90418 -         ..
F90419 -    2.  The lesson from topic mapping is that *everything* in some
F90420 -        universe of discourse is a subject.  Every subject warrants a
F90421 -        *locater* in some database.  If we are talking "hyperdatabase"
F90422 -        (distributed), then each individual database location becomes
F90423 -        part of the locater of each subject.  When I say everything, I
F90424 -        really mean it. Asserted relationships are also subjects.
F90426 -         ..
F90427 -    3.  I don't see any reason why contacts should be treated any
F90428 -        differently than the other subjects, each of which is some axis
F90429 -        of poims.
F90430 -
F90431 -           [...note on 080506 Jack submitted a letter with a file
F90432 -           attached of a picture that illustrates a topic map that
F90433 -           seems similar to dialog maps and issue maps.  Have not had
F90434 -           time to enter it in the record.
F90436 -            ..
F90437 -           [...below, Morris has previously observed everything is
F90438 -           cross-connected. ref SDS 0 ZJ4V
F90440 -            ..
F90441 -           [...below, in follow up letter Jack comments again on
F90442 -           cross-connections. ref SDS 0 QV6T
F90444 -         ..
F90445 -    4.  With locaters, you can for so-called RESTful URLs to access the
F90446 -        subjects directly.  If you then use various forms of
F90447 -        hierarchical organization within each subject, then you use
F90448 -        xpath to access nodes in each subject's graph.
F90449 -
F90451 -  ..
F90452 - Everything Connected Everything Else Contacts Base Subject Identifier
F90453 -
F90454 - Below, chronology, context, and connection explains why everything in
F90455 - SDS is in the right place at the right time. ref SDS 0 ZJ3H
F90457 -  ..
F90458 - Everything connected to everything else was considered in relation to
F90459 - a book Jack referenced on 070729 presenting the common practice of
F90460 - filing everything miscellaneous. ref SDS 98 HE6N  The design for
F90461 - Knowledge Management that integrates chronology, context, and
F90462 - connection converts chaos of miscellaneous filing into order that
F90463 - yields the power of knowledge. ref SDS 98 738G  Everything connected
F90464 - to everything else offers a powerful corollary to everything is
F90465 - miscellaneous. ref SDS 98 K33H
F90466 -
F90467 -
F90468 -
F905 -

Technologies of Cooperation Paper by Authors Andrea Saveri Howard Rh

FH03 -
FH0401 -  ..
FH0402 - Recently, Jack submitted a link to a paper dated January 2005 and
FH0403 - explains open source development for knowledge management...
FH0404 -
FH0405 -        Technologies of Cooperation
FH0406 -
FH0407 -    
FH0409 -         ..
FH0410 -        Executive Summary...
FH0412 -         ..
FH0413 -        Emerging digital technologies present new opportunities for
FH0414 -        developing complex cooperative strategies that change the way
FH0415 -        people work together to solve problems and generate wealth.
FH0416 -        Central to this class of cooperation-amplifying technologies
FH0417 -        are eight key clusters, each with distinctive contributions to
FH0418 -        cooperative strategy:, ref OF 1 PPXS
FH0420 -  ..
FH0421 - Computer networks seem to be a central theme of the paper "Tools for
FH0422 - Cooperation. ref OF 1 1314
FH0423 -
FH0424 -             [On 071220 letter to Jack comments on the paper with
FH0425 -             questions. ref SDS B2 IK5H
FH0427 -  ..
FH0428 - Jack does not explain how networks with tools for cooperation social
FH0429 - collectives, etc., solve the problem of everything filed
FH0430 - "miscellaneous," put forward in his letter on 070729, ref SDS 98 HE6N,
FH0431 - and discussed further below. ref SDS 0 ZJ3H
FH0433 -  ..
FH0434 - There is no discussion in the paper about how to work quickly with
FH0435 - network technology and also accurately to avoid meaning drift and
FH0436 - false knowledge, explained in POIMS, ref OF 11 049O, using
FH0437 - traceability to original sources throughout networks, ref OF 10 1X6G,
FH0438 - as further called out in professional standards, reviewed on 950721.
FH0439 - ref SDS 18 1740
FH0440 -
FH0441 -
FH0442 -
FH0443 -
FH0444 -
FH0445 -
FH05 -

Alphabet Technology Literacy Writing Reading Amplifies Power of Thin

GK03 -
GK0401 -  ..
GK0402 - Printing Press Extended Power Alphabet Amplify Power of Thinking
GK0403 - Alphabet Technology Improved with Technology to Lift Civilization
GK0404 -
GK0405 - The paper describes writing as a strategic technology that amplifies
GK0406 - the power of thinking, ref OF 1 0358, through the process of literacy,
GK0407 - and which was eventually extended by the printing press. ref OF 1 PK4X
GK0408 - This supports POIMS explanation of alphabet technology, ref OF 10
GK0409 - ER3G, and research on 991108 describing the "alphabetic mind" derived
GK0410 - from an "explosive technology." ref SDS 29 5628  On 010622 Douglas
GK0411 - Lenat maintains that cognitive technology of signs and symbols makes
GK0412 - people "superhuman." ref SDS 65 N668  Literacy is further explained on
GK0413 - 940609, ref SDS 15 8854, following up work on 930112. ref SDS 13 3443
GK0414 -
GK0415 -            [On 071220 letter to Jack asks if submission of the paper
GK0416 -            on Technologies of Cooperation begins review of alphabet
GK0417 -            technology planned on 011208? ref SDS B2 QK5J
GK0419 -             ..
GK0420 -            [On 080127 the paper Jack submitted on Techologies of
GK0421 -            Cooperation was cited in a letter to Morris on the role of
GK0422 -            alphabet technology to lift civilization, ref SDS B6 OM4U,
GK0423 -            and noting that Jack does not support this part of the
GK0424 -            paper. ref SDS B6 OM5R
GK0426 -  ..
GK0427 - On 991010 development of the printing press, credited to Gutenberg in
GK0428 - approximately 1455, was as well the most powerful technology to
GK0429 - advance civilization during the past 1000 years, i.e., for the
GK0430 - millenium. ref SDS 27 2548
GK0432 -  ..
GK0433 - The authors of "Tools for Cooperation" say in part...
GK0434 -
GK0435 -        What we are witnessing today is thus the acceleration of a
GK0436 -        trend that has been building for thousands of years.  When
GK0437 -        technologies like alphabets and Internets amplify the right
GK0438 -        cognitive or social capabilities, old trends take new twists
GK0439 -        and people build things that never could be built before.
GK0440 -        ref OF 1 1294
GK0442 -  ..
GK0443 - Seems to reflect prospects presented in POIMS for a new way of working
GK0444 - with the alphabet that lifts capacity to think, remember, and
GK0445 - communicate not previouosly possible, and which necessarily lifts
GK0446 - civilization to a new plateau. ref OF 14 3742
GK0448 -  ..
GK0449 - Jack commented previously on improving alphabet technology for
GK0450 - leveraging intelligence, reported 011208. ref SDS 71 4Q5L  Others have
GK0451 - also had difficulty understanding the role of the alphabet.
GK0452 - ref SDS 71 R63Q
GK0454 -  ..
GK0455 - At that time, Jack planned to review this issue in order to assess
GK0456 - prospects for SDS to augment intelligence. ref SDS 71 456G  Is the
GK0457 - reference to "Tools for Cooperation" part of that review process?
GK0458 -
GK0459 -     [On 071220 letter to Jack asks if submission of the paper on
GK0460 -     Technologies of Cooperation begins review of alphabet technology
GK0461 -     planned on 011208? ref SDS B2 QK5J
GK0463 -      ..
GK0464 -     [On 071220 Jack clarifies mention of alphabet technology in the
GK0465 -     paper he submitted Technologies of Cooperation was coincidental
GK0466 -     rather than an effort to study SDS, POIMS, and alphabet
GK0467 -     technology; he feels alphabet technology is too abstract for his
GK0468 -     thinking and his audience. ref SDS B2 RH6L
GK0469 -
GK0470 -
GK0471 -
GK0472 -
GK0473 -
GK05 -

Technologies of Cooperation Computer Network Centric Organization Op

H003 -
H00401 -  ..
H00402 - Cooperation Networks Knowledge Management for Social Collectives
H00403 - Networks Enable Cooperation Social Collectives Knowledge Management
H00404 -
H00405 - Seems to promote open source, ref OF 2 S164, social computer
H00406 - networking, ref OF 2 SZ8N, that facilitates everybody contributing,
H00407 - collaborating, and cooperating, ref OF 1 PPXS, along the lines of Doug
H00408 - Engelbart's OHS/DKR project.  The meeting at SRI on 000324 described
H00409 - networking to enable "bootstrap" efforts discovering and developing
H00410 - emergent tools, and systems for solving world problems. ref SDS 37
H00411 - 4877 Jack's Nexist software with follow on development of CALO and
H00412 - Iris at SRI have continued this work, reviewed on 060211. ref SDS 90
H00413 - 0001
H00415 -         ..
H00416 -        [On 071220 letter to Jack notes paper supports networking with
H00417 -        open source technologies. ref SDS B2 RH6I
H00419 -  ..
H00420 - Many technology solutions are presented in the paper for accomplishing
H00421 - better cooperation.  These are summarized in a matrix that sets
H00422 - criteria and scope with a "strategic map of technologies for
H00423 - cooperation." ref OF 1 04E2  Previously, on 020608 John Maloney noted
H00424 - that SDS does not fit any of the accepted tools for Knowledge
H00425 - Management, reported 020610. ref SDS 74 N16F  Below, SDS intelligence
H00426 - support for making sense of complexity complements established tools
H00427 - people have accepted for Knowledge Management. ref SDS 0 DY5M
H00429 -  ..
H00430 - Boeing was looking into "network centric" organizations, reported on
H00431 - 060317. ref SDS 91 P357
H00433 -  ..
H00434 - John Maloney promotes Knowledge Management for fantastic social
H00435 - relationships, reported on 010114. ref SDS 60 EK3I  Larry Prusak while
H00436 - at IBM helped launch Knowledge Management in 1993 to improve
H00437 - productivity, reported on 011102. ref SDS 68 K37K  Eventually, Larry
H00438 - and his colleagues settled on using networks, ref SDS 69 5C6M, to
H00439 - improve conversation. ref SDS 69 H461
H00441 -  ..
H00442 - "Technologies of Cooperation" mentions nothing about the role of
H00443 - networks to implement Doug Engelbart's proposal on 000405 adding links
H00444 - to email with granular addressability. ref SDS 42 2484  On 070831
H00445 - report that addressability was abandoned because using explicit links
H00446 - to improve accuracy of daily work takes too much time finding sources
H00447 - to link. ref SDS A0 FM3F
H00448 -
H00449 -
H00450 -
H00451 -
H005 -

Chronology Context Connection Complementary Add Intelligence Convert

HK03 -
HK0401 -  ..
HK0402 - Things We Don't Talk About Around Hear SDS POIMS NWO
HK0403 - Knowledge Management Intelligence Communication Metrics Support Missing
HK0404 - Chronology Context Connection Complement Technologies of Cooperation
HK0405 - Complementarity Leverages Technologies of Cooperation with POIMS
HK0406 -
HK0407 - The paper uses "social" 145 times and "collective" 42 times in 30
HK0408 - pages.  By contrast, "chronology" is mentioned once, ref OF 3 TV36,
HK0409 - context is used 10 times, often with "environment." "Connection" is
HK0410 - not used at all in the paper.
HK0412 -  ..
HK0413 - There is a good discusison of using the Internet for linking people
HK0414 - into groups, described as "blogs." ref OF 3 TV36  Links are not
HK0415 - explained for connecting cause and effect to augment intelligence, nor
HK0416 - for quickly verifying accuracy, i.e., authentic communication, and for
HK0417 - context to expand understanding, as set out in NWO.
HK0418 -
HK0419 -        [On 071220 letter to Jack Park notes paper on "Tools of
HK0420 -        Cooperation" does not discuss links for expanding the power of
HK0421 -        knowledge to connect cause and effect; and it cites the letter
HK0422 -        from Murray Altheim on 020620 that says people do no use links
HK0423 -        to expand the power of knowledge because creating links takes
HK0424 -        too much time using conventional toosl. ref SDS B2 KW4O
HK0426 -  ..
HK0427 - The role of tools to manage chronology, context, and connection,
HK0428 - explained in POIMS, ref OF 13 8555, appears therefore to complement
HK0429 - "Technologies of Cooperation" contemplated by the authors, per above,
HK0430 - ref SDS 0 ON4I, and noted previously on 020610. ref SDS 74 N16F  USACE
HK0431 - reported that POIMS support for Communication Metrics improves
HK0432 - cooperation and collaboration. ref DRP 5 4582  Requirements for
HK0433 - complementarity to make paperless office efficiencies productive
HK0434 - applying electronic records management were reviewed on 890523.
HK0435 - ref SDS 1 LV59
HK0437 -  ..
HK0438 - Jack's letter on 000504 to the OHS/DKR team meeting at SRI disclosed
HK0439 - SDS capabilities venturing beyond acceptable views are "things we
HK0440 - don't talk about around here." ref SDS 43 XD5M  At that time in 2000,
HK0441 - there was a lot of talk about electronic storage in a "knowledge
HK0442 - repository," and about "metadata" to organize the record, and about
HK0443 - linking to connect the record, but, like "Technologies of
HK0444 - Cooperation," there was no consideration of "time," and none about
HK0445 - "complementarity," which is essential for productivity of any
HK0446 - "paperless office" effort, sometimes called "Knowledge Management,"
HK0447 - and shown by review on 960304 of the Vannevar Bush article in 1945.
HK0448 - ref SDS 20 GX59
HK0449 -
HK0450 -        [On 071220 letter to Jack Park asks if Knowledge Management
HK0451 -        professionals are beginning to recognize the role of
HK0452 -        chronology, context, and connection? ref SDS B2 WL5T
HK0454 -  ..
HK0455 - "Knowledge Collective" presented in "Technologies of Cooperation,"
HK0456 - ref OF 4 TX6W, may be another term for "knowledge repository" and
HK0457 - "network." ref OF 4 TX6W  There is no evident effort in the paper to
HK0458 - define "knowledge" along the lines shown in POIMS, ref OF 10 0367, and
HK0459 - within academic disciplines of cognitive science, philosophy, nor from
HK0460 - "experience" of daily life applying the physics of causation, e.g.,
HK0461 - the locality principle, shown in NWO. ref OF 19 I38N  Equally, there
HK0462 - is no effort to distinguish knowledge from information, which was
HK0463 - called out by Doug Engelbart on 000307 for work at SRI on the OHS/DKR
HK0464 - project. ref SDS 36 4820  Case study on 020608 shows challenge of
HK0465 - moving beyond information management. ref SDS 73 CC6J
HK0467 -  ..
HK0468 - "Feedback" is emphasized, e.g., ref OF 1 04UQ, without explanation of
HK0469 - strategies to overcome resistance, explained in NWO, ref OF 21 2670,
HK0470 - and discussed with Justice Mosk on 911130. ref SDS 10 K64L and
HK0471 - ref SDS 10 P29N  SDS fills the void with proven tools and 8-steps of
HK0472 - Communication Metrics for comprehensive feedback. ref OF 13 685K (see
HK0473 - specifically step 8. ref OF 13 365F)  This record is an example,
HK0474 - following up Jack's submission of the paper, per above. ref SDS 0 FU6I
HK0476 -  ..
HK0477 - "Metadata" is mentioned briefly by the authors and for the purpose of
HK0478 - viewing traffic on web pages (social spaces), ref OF 3 TU82, and
HK0479 - without explanation nor hint that context management for organizing
HK0480 - the record is central to making connections that yield the power of
HK0481 - knowledge, as set out POIMS. ref OF 13 1110  Nothing is evident to
HK0482 - solve the problem Jack reported in referencing the book on filing
HK0483 - everything "miscellaneous," reported on 070729. ref SDS 98 HE6N
HK0484 - Neither is Jack's point in his letter today meaningfully considered in
HK0485 - the paper about everything being connected to everything else, which
HK0486 - impacts prospects for effective cooperation, per above. ref SDS 0 IV5F
HK0488 -  ..
HK0489 - Silence on context management to organize the record of daily work
HK0490 - aligns with case study on 070126 showing people have given up.
HK0491 - ref SDS 93 WV5K  Reflects failure to develop tools that make subject
HK0492 - index seem not to be beyond reach, illustrated by the article reported
HK0493 - on 910418. ref SDS 7 5584  Jack Park described context management,
HK0494 - called "ontology" in his work, as a "pandora's box," reviewed on
HK0495 - 000221. ref SDS 33 L58O
HK0496 -
HK0497 -        [On 071212 Morris shocked, overwhelmed by detail in SDS subject
HK0498 -        index that organizes the record for context management.
HK0499 -        ref SDS B0 ZJ3H
HK0501 -  ..
HK0502 - "Sense making" has a single sentence, ref OF 4 TZ61, also, without
HK0503 - explanation of adding intelligence showing chronology, correlations,
HK0504 - implications and nuance in routine data streams, explained in POIMS.
HK0505 - ref OF 10 0367  The "report" process in SDS strives to make sense of
HK0506 - complexity arising from the constant flow of daily working
HK0507 - information. ref OF 12 2300  Jack Park explained goals for technology
HK0508 - to aid sensemaking in his letter on 040622. ref SDS 85 FM5W
HK0509 -
HK0510 -
HK0511 -
HK0512 -
HK0513 -
HK0514 -
HK06 -

Everything Connected Everything Else Subject Indexing Difficult Comp

IU03 -
IU0401 -  ..
IU0402 - Everything Connected Makes Everything in Right Place Right Time
IU0403 -
IU0404 - Submitted a response to Jack's letter this morning on everything being
IU0405 - a pointer to everything else, ref SDS 0 IV5F, and saying...
IU0406 -
IU0407 -    1.  Subject: SDS Contacts Everything Subject Pointer to Everything Else
IU0408 -        Date: Mon, 12 Nov 2007 14:05:30 -0800
IU0412 -         ..
IU0413 -    2.  Jack,
IU0415 -         ..
IU0416 -    3.  I agree with your idea about mapping Contacts to everything;
IU0417 -        this was addressed recently on 071010. ref SDS A5 1573
IU0419 -         ..
IU0420 -    4.  On 980405, Morris commented on everything being a pointer to
IU0421 -        everything else. ref SDS 24 2532
IU0422 -
IU0423 -           [...below, in follow up letter Jack comments again on
IU0424 -           cross-connections. ref SDS 0 QV6T
IU0425 -
IU0426 -           [...below, in another follow up letter Jack cites Welch
IU0427 -           comments, ref SDS 0 M14K, and then clarifies topic maps
IU0428 -           cross classes of personal and organizational contacts.
IU0429 -           ref SDS 0 M17R
IU0431 -  ..
IU0432 - Morris also cited complexity of subject indexing that arises with
IU0433 - "fractionalized subjects," discussed on 970116. ref SDS 22 1732
IU0435 -  ..
IU0436 - Support for chronology, context, and connection explained in POIMS,
IU0437 - ref OF 12 8555, fits the model presented in Jack's letter earlier
IU0438 - today, ref SDS 0 IV5F, and explains why everything in SDS is in the
IU0439 - right place at the right time, noted by Morris on 010425. ref SDS 62
IU0440 - EP7F  Cross-referencing specific details with multiple contexts
IU0441 - reduces entropy by adding order to complex correlations, implications,
IU0442 - and nuance.  USAFIT noted that rising entropy causes management
IU0443 - failure, reviewed on 970707. ref SDS 23 0108  Reducing entropy
IU0444 - increases chances of finding relevant details in time to be effective
IU0445 - saving lives, time, and money.
IU0446 -
IU0447 -
IU0448 -
IU0449 -
IU05 -

Cross-fertilization Parallel Efforts Meeting Schedule Too Pushy Coll

JM03 -
JM0401 -  ..
JM0402 - Collaboration Helpful Transformation to Culture of Knowledge
JM0403 - Meeting Schedule Collaborate Knowledge Management SDS Development
JM0404 - Knowledge Management Collaboration Meeting Communicating Contributing
JM0405 -
JM0406 - A few weeks ago, correspondence suggested Morris and I would meet with
JM0407 - Jack at SRI to review ideas on SDS development.  This followed initial
JM0408 - considerations for Jack to meet with us at Morris' place in Saratoga.
JM0410 -  ..
JM0411 - Several recent letters have asked Jack about implementing these plans
JM0412 - to meet, and Jack has not responded.  Therefore, asked about this
JM0413 - again....
JM0415 -  ..
JM0416 - Letter to Jack continues...
JM0417 -
JM0418 -    5.  Hope I am not being too pushy.  If you have changed your mind
JM0419 -        and don't want to meet just say so, and similarly if
JM0420 -        collaboration on SDS has no appeal, I will stop bothering you
JM0421 -        with this stuff.  I realize you have a lot of "irons in the
JM0422 -        fire."  Sometimes cross-fertilization can aid parallel efforts,
JM0423 -        if the right mix of people can collaborate.
JM0424 -
JM0425 -            [...below, Jack reports contributing ideas for "fun," with
JM0426 -            no serious intent about learning to advance from
JM0427 -            information to a culture of knowledge. ref SDS 0 VY7X
JM0429 -             ..
JM0430 -            [...below, Jack reports not having enough time for meeting
JM0431 -            to collaborate on Knowledge Management. ref SDS 0 QV9O
JM0432 -
JM0438 -
JM0439 -
JM0440 -
JM05 -

Iris Close SDS Java Slow Performance SDS Using DOS Makes Structured

KS03 -
KS0401 -  ..
KS0402 - Java XML Technology Iris Not Far from SDS
KS0403 - Iris Not Far from SDS Jack Contributing for Fun
KS0404 - Fun Contributing SDS Work Java Developing IRIS Needs Work Product
KS0405 - Work Product Missing Knowledge Management Technologies Except SDS
KS0406 -
KS0407 -
KS0408 - Jack's 2nd letter continues...
KS0409 -
KS0410 -    8.  Keep in mind that I'm just contributing ideas for fun here.
KS0411 -        Most of my real work is performed only on open source projects.
KS0412 -        OpenIRIS [1] already has tons of useful code that could be
KS0413 -        imported into an SDS project. Indeed, OpenIRIS isn't all that
KS0414 -        far from SDS anyhow. But, it's Java.
KS0415 -
KS0416 -     
KS0418 -  ..
KS0419 - SDS yields work product like this record.  There is no evidence other
KS0420 - tools produce Knowledge Management work product.  On 070904 report
KS0421 - that activity on collaboration network supporting explicit links,
KS0422 - called purple numbers, has ended after 4 years or so of never having
KS0423 - used the core capability of connecting one thought to another.
KS0424 - ref SDS A1 DV5R  On 070126 case study indicates everybody has given up
KS0425 - on Knowledge Management. ref SDS 93 QH8L
KS0427 -  ..
KS0428 - Jack reported on 060129 that people are not using Iris for daily work
KS0429 - on the job. ref SDS 89 7A4F
KS0431 -  ..
KS0432 - SDS transforms the drudge of "diligence" doing hard work for Knowledge
KS0433 - Management, reported on 000307, ref SDS 36 767G, to a paradigm of
KS0434 - having fun working intelligently, reviewed on 070904. ref SDS A1 DV7P
KS0435 - POIMS explains efficient usability makes using the computer like
KS0436 - playing a piano. ref OF 13 6M5H  This was reported to the team at SRI
KS0437 - in a letter on 001004, ref SDS 48 6N9G, citing analogy of "playing a
KS0438 - piano. ref SDS 48 GR5L  Making good management fun was mentioned again
KS0439 - in a follow up letter on 001121. ref SDS 53 PK6M
KS0441 -  ..
KS0442 - Iris was reviewed on 060211, ref SDS 90 ZG5K, including case study of
KS0443 - Java web-application for collaboration on the Internet. ref SDS 90
KS0444 - YY5K  Iris documentation mentions "artificial intelligence" and
KS0445 - "Knowledge Management." ref SDS 90 F443  SDS strives to leverage
KS0446 - intelligence, explained in POIMS, ref OF 12 6649, using 8-steps for a
KS0447 - practice of Communication Metrics, also, set out in POIMS. ref OF 12
KS0448 - 685K  Knowledge Management is therefore a common goal for Iris and
KS0449 - SDS.
KS0451 -  ..
KS0452 - Slow performance using Iris was reported on 060211, ref SDS 90 055L,
KS0453 - cited again by Gary Johnson today in connection with Java technology,
KS0454 - per above, ref SDS 0 LY7W, and considering XML editor for SDS, also,
KS0455 - above. ref SDS 0 446N
KS0456 -
KS0457 -            [On 071127 denial of service attacks present significant
KS0458 -            risks to Internet-based applications. ref SDS A7 X95H
KS0460 -             ..
KS0461 -            [On 080104 Morris considering Java Data Object programming
KS0462 -            for SDS Windows application. ref SDS B4 8O5H
KS0464 -  ..
KS0465 - Iris website says in part...
KS0466 -
KS0467 -              http:/
KS0468 -
KS0469 -        The most important issues to know about are:
KS0470 -
KS0471 -        PDFs can crash IRIS (#IRI-351): If you have not upgraded to
KS0472 -        Acrobat 7.0, opening a PDF file can freeze IRIS.
KS0474 -         ..
KS0475 -        Speed (#419, #464, #467): Installing IRIS is slow. IRIS is
KS0476 -        very slow on startup the first time, only a bit faster
KS0477 -        subsequent times, and during use, has functionality that needs
KS0478 -        to be dramatically optimized.
KS0480 -  ..
KS0481 - The User's Manual in PDF format (without explicit links for granular
KS0482 - addressability) says in Section 2.2 Installing IRIS...
KS0483 -
KS0484 -        The Installer displays a window confirming the beginning of
KS0485 -        installation.  Installation includes loading of the Java
KS0486 -        Virtual Machine environment, OAA environment, and IRIS
KS0487 -        software.
KS0489 -  ..
KS0490 - Contributing for "fun" noted in Jack's letter today, ref SDS 0 VY7X,
KS0491 - aligns with experience supporting Doug Engelbart during 2000, listed
KS0492 - on 001017. ref SDS 50 1575  With no value at risk nor evident need to
KS0493 - add value for product development, there is little incentive to make
KS0494 - the effort of cognitive overhead required for meaningful progress,
KS0495 - from considerations on 001126 learning to use SDS in order to learn
KS0496 - Knowledge Management. ref SDS 56 M171
KS0498 -  ..
KS0499 - Besides having fun "talking" about Knowledge Management in meetings,
KS0500 - calls, and email, noted by John Maloney on 010114, ref SDS 60 EK3I,
KS0501 - people can have more fun saving lives, time, and money making sense of
KS0502 - complex daily work, noted by Doug Engelbart on 000327. ref SDS 38 3971
KS0503 -
KS0504 -        [On 071128 Kaiser reversed position of denying payment for
KS0505 -        treatment in a clinical trial, saving the patient $15K - $20K
KS0506 -        per year. ref SDS A8 TH8L
KS0508 -         ..
KS0509 -        [On 080104 people feel SDS is effective becasue Rod is
KS0510 -        diligent, and overlook that SDS makes working intelligently
KS0511 -        fun. ref SDS B4 EM9F
KS0512 -
KS0513 -
KS0514 -
KS0515 -
KS0516 -
KS0517 -
KS0518 -
KS06 -

Busy Not Enough Time Meet Collaborate Help Contribute SDS Developmen

LY03 -
LY0401 -  ..
LY0402 - SDS Hope Success Without Meeting Helping Goal for Many
LY0403 - Busy No Time Meet Deliberate Collaborate on Advancing Civilization
LY0404 -
LY0405 - Jack further responded saying he is too busy to collaborate on SDS,
LY0406 - responding to letter earlier today. ref SDS 0 RQ4H
LY0407 -
LY0433 -  ..
LY0434 - Chiming in with spontaneous comments aligns with the report today on
LY0435 - having "fun," which fits the model of open source development for the
LY0436 - OHS/DKR project at SRI in 2000, reported on 001017, ref SDS 50 1575,
LY0437 - and cited above. ref SDS 0 VY7X
LY0439 -  ..
LY0440 - In a letter on 070904, Gary cited slow progress developing Knowledge
LY0441 - Management due to lack of focus, ref SDS A1 DV9U, which commonly
LY0442 - occurs in organizations constrained by cultural forces that drive
LY0443 - conformity. ref SDS A1 F23M
LY0445 -  ..
LY0446 - During the meeting with Morris today, explained planning to meet at
LY0447 - SRI has been deferred due to Jack's heavy schedule reported in his
LY0448 - letter today, per above. ref SDS 0 QV5X
LY0449 -
LY0450 -
LY0451 -
LY0452 -
LY0453 -
LY0454 -
LY05 -

Everything Subject Pointer Topic Map Data Base Unique Locators with

M303 -
M30401 -  ..
M30402 - Everything Subject Pointer Topic Map Data Base Unique Locators
M30403 -
M30404 - Jack clarifies and expands on earlier comments today about everything
M30405 - connected to everything else. ref SDS 0 ZJ3H and ref SDS 0 IV5F
M30406 -
M30429 -
M30430 -
M30431 -
M30432 -
M305 -

Contacts Personnel File Personal Integrate Organizational Recursive

M703 -
M70401 -  ..
M70402 - Personnel File Part Personal Contacts Stable Data
M70403 - Jack Comments 1 Data Base Personal Organizational Contacts Data Base
M70404 - Contacts Integrate Personal Organizational into One Data Base
M70405 -
M70406 - Jack comments in another letter on integrating organizational and
M70407 - personal contact data bases, per above. ref SDS 0 MI46
M70408 -
M70409 -    1.  Subject:  SDS Contacts Design Integrate Organizational and Personnel Records
M70410 -        Date: Mon, 12 Nov 2007 15:40:47 -0800
M70415 -         ..
M70416 -    2.  Rod wrote....
M70417 -
M70418 -          I agree with everything you propose. [referring to Gary's
M70419 -          idea on integrating personal and organizational contact data
M70420 -          bases into a single data base. ref SDS 0 MI46]
M70421 -
M70422 -          I think Morris has a similar idea in mind about integrating
M70423 -          organizational and personal records.  This will require some
M70424 -          experimenting and then experience to test efficacy, but
M70425 -          something along these lines seems likely.
M70427 -           ..
M70428 -          We have not actually said this, but in some respects the
M70429 -          "Personal" Contact data base is similar to a "Personnel" file
M70430 -          on an individual, which might contain payroll data, vacation
M70431 -          history, etc.
M70433 -         ..
M70434 -    3.  Jack Comments...
M70436 -         ..
M70437 -        As the class of subjects: Person has the subclass Personnel,
M70438 -        new attributes (properties, relationships) occur on each
M70439 -        instance. So, if you create an employee (personnel instance)
M70440 -        Joe BagODonuts, that instance inherits all sorts of person
M70441 -        identity properties, plus the personnel identity properties
M70442 -        (employee#, etc), and then relationships which include payroll
M70443 -        data, vacation history, etc.  Subject-centric forces you to do
M70444 -        things that way if you choose that discipline.
M70446 -  ..
M70447 - Some of the scope Jack discusses may be part of Contacts subject
M70448 - index, also, noted above, ref SDS 0 ZJ3H, citing recent work on
M70449 - 071010, ref SDS A5 1573, and which complements the Contacts system.
M70450 -
M70451 -
M70452 -
M70453 -
M705 -

Contacts Records Transferrable Between Users and Organizations Data

MU03 -
MU0401 -  ..
MU0402 - Transferrability Contacts Between Individual to Organization
MU0403 -
MU0404 -
MU0405 -    4.  Rod wrote...
MU0406 -
MU0407 -          A major use case is transferability.  Say you join the
MU0408 -          company.  Would like for the personnel manager, project
MU0409 -          manager, or somebody to go through and select a body of
MU0410 -          personal contacts from a company or project master list,
MU0411 -          perhaps with sensitive data redacted, so that everyone does
MU0412 -          not have to do the same data entry all over again just to get
MU0413 -          up to speed.  You will bring your own contacts.  These need
MU0414 -          to be added  to the new stuff.  But are all of your original
MU0415 -          Contacts added to the Company master list?  Seems like "no";
MU0416 -          but, things get very complicated very quickly.
MU0417 -
MU0419 -         ..
MU0420 -    5.  Jack Comments...
MU0421 -
MU0422 -        Rights and permissions can be attached to every property
MU0423 -        attached to each subject.  A subject is represented by a
MU0424 -        container we call a SubjectProxy; it is a container for a Set
MU0425 -        (in the set theoretic sense -- no duplicates) of
MU0426 -        SubjectProperty objects (Key-Value pairs).  You can hang rights
MU0427 -        and permissions on each of those, and assign roles to each user
MU0428 -        roaming about the database.
MU0429 -
MU0430 -
MU0431 -
MU0432 -
MU05 -

Contacts Screens Pending Revisions Expand Code from Review Today Tel

ND03 -
ND0401 -  ..
ND0402 - Contacts Screens Pending Revisions and Expand Code from Review Today
ND0403 -
ND0404 - Follow up ref SDS A6 XH6K.
ND0405 -
ND0406 - Morris submitted a paper this morning, which says in part...
ND0407 -
ND0408 -    This is the definitions for the SDS Contacts System...
ND0410 -  ..
ND0411 - The paper has some of the code he has created to define Contact data
ND0412 - structures.  This will be expanded to begin constructing program
ND0413 - screens, planned on 071106 for review today. ref SDS A6 JR97
ND0415 -  ..
ND0416 - He has not had time to review SDS Contacts data structures, shown on
ND0417 - 071106. ref SDS A6 0R4H  Review today, including discussion with Gary
ND0418 - provided guidance to revise initial code.
ND0419 -
ND0420 -
ND0421 -
ND0422 -
ND05 -

Planning Follow Up SDS Windows Application Contacts Data Base Expand

NT03 -
NT0401 -  ..
NT0402 - Follow Up Planning and Opportunities
NT0403 -
NT0404 - Follow up ref SDS A6 JR97, ref SDS A2 JR97.
NT0405 -
NT0406 - Over the next few weeks, Morris will continue code started during the
NT0407 - meeting on 071106 to produce screens and initial functionality.
NT0409 -  ..
NT0410 - Will call on Sunday 071202 to schedule another meeting for review and
NT0411 - further product planning on Monday or Tuesday.
NT0412 -
NT0413 -
NT0414 -
NT0415 -
NT0416 -
NT0417 -
NT0418 -
NT05 -