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


S U M M A R Y


DIARY: June 1, 2000 02:40 PM Thursday; Rod Welch

Letter from Paul Fernhout with proposal on SDS.

1...Summary/Objective
2...SDS Provides Helpful Development Path for Knowledge Management
.....Multiple Windows Overwhelms Span of Attention
.....Knowledge Space Hard to Navigate Because Many Windows Open
..........Intelligence May Lead to Knowledge to Solve World Problem
3...Navigation Aids (Map) Can Enhance SDS on the Internet
....Search Capability for SDS on the Internet
.......Paul's Work Supports "Story" as Central to Learning
4...Privacy, Confidentiality, Security Need More Work in SDS
5...Email Improved by SDS Webmail
6...Proposal for Navigation, Interaction Tools for SDS on Internet
...........Original Work Unchanged, Use Traceability Original Sources
...........Collaboration Preserves Original Work, Traceability
...........Dynamic KM System Supports Thinking, Doing, Collaboration
7...Paul cites negative forces against the proposal...
8...Friendly forces favoring the proposal...
9...Paul requests ideas on what makes sense.

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

1...Seems like there are settings that control whether links open
2...Possibly Paul could provide a link to an example, provide a

CONTACTS 

SUBJECTS
Alliances
Windows Open For Links Confusing
Fernhout Commends SDS for Knowledge Management
Links Open in Same Not Multiple Windows, 000601
Fernhout Application Process SDS Record
Fernhout, Paul, 000601
SDS Links Cause Confusion Because Too Many Windows are Opened at Once
SDS Links Complexity Overwhelming Too Many Windows Open at Once, Paul

1410 -    ..
1411 - Summary/Objective
1412 -
141201 - Follow up ref SDS 87 0000, ref SDS 86 0000.
141202 -
141203 - Paul has reviewed Communication Metrics and SDS record on the web. He
141204 - likes some features, but reports problem of getting confused by having
141205 - too many links open at the same time. ref SDS 0 0894  He proposes
141206 - developing an open source solution based on his Pointrel Data
141207 - Repository system. ref SDS 0 0035
141208 -
141209 - Sent interim response saying I will contact him in a few days.
141210 -
141229 -
141230 -     [On 000608 sent Paul response linked to this record. ref SDS 99
141231 -     0001
141232 -
141233 -
141234 -
141235 -
1413 -
1414 -
1415 - Progress
141601 -  ..
141602 - SDS Provides Helpful Development Path for Knowledge Management
141603 -
141604 - Received ref DRT 1 0001 from Paul Fernhout, a contributor to the DKR
141605 - project Doug Engelbart has underway, meeting at SRI.
141607 -  ..
141608 - Paul indicates having reviewed Welchco home page explaining
141609 - Communication Metrics, and he reviewed SDS records on the web. He is
141610 - favorably impressed, as planned in porting SDS to the web on 971021.
141611 - ref SDS 7 3636
141612 -
141613 -     [On 000613 Paul commends SDS and Com Metrics on the Internet to
141614 -     the DKR team meeting at SRI. ref SDS A1 0001
141620 -  ..
141621 - Paul cites review of his letter on 000405 that explained data
141622 - structures for the DKR, ref SDS 65 3705, which was cited recently on
141623 - 000524 discussing his Pointrel Data Repository system. ref SDS 90 3240
141624 - Paul notes today that he would have liked to have been notified of
141625 - analysis on 000405 in order to comment. ref DRT 1 0713
141627 -  ..
141628 - Paul appreciated review of his Pointrel Data Repository system, which
141629 - he described in a letter to Eric Armstrong, ref DRT 1 2924, submitted
141630 - on 000524. ref SDS 90 0783,
141631 -
141633 -      ..
141634 -     Multiple Windows Overwhelms Span of Attention
141635 -     Knowledge Space Hard to Navigate Because Many Windows Open
141636 -
141637 -     Paul agrees that SDS on the Internet is hard to navigate, cited by
141638 -     Eric Armstrong on 000405, ref SDS 65 4823, later on 000504,
141639 -     ref SDS 77 1739, and most recently in a meeting at Intel on
141640 -     000517. ref SDS 88 5184, and by others beginning on 970712.
141641 -     ref SDS 9 6804 and 970824. ref SDS 10 4920
141642 -
141643 -         [On 001116 Paul reports SDS is inspirational; it shows KM can
141644 -         improve understanding and productvity. ref SDS A3 H23M
141646 -      ..
141647 -     Paul says today the problem is Welchco packs so much information
141648 -     and links together that it demonstrates the weakness of HTML-based
141649 -     hypertext for handling complex data.  In short, HTML is designed
141650 -     for one view of data -- but with complex data you often want to
141651 -     view the same data but in different ways depending on your search
141652 -     motivation or level of understanding (e.g. introduction, overview,
141653 -     tutorial, thread following, subject based). ref DRT 1 1584
141654 -
141655 -         [On 001219 Paul worried that complexity is greater concern
141656 -         than energy problem. ref SDS A4 9I6K
141657 -
141658 -         [On 010122 BrowseUp proposes priority and filtering to manage
141659 -         a lot of links. ref SDS A5 VC7L
141661 -      ..
141662 -     Paul explains the problem as "... right now I have about twenty
141663 -     Netscape windows open from trying to follow various topical
141664 -     threads via links on Welchco. There is so much interesting content
141665 -     I lose track of why I opened each window, or which window links
141666 -     back to a previous topic. Browsers also provide limited context of
141667 -     just exactly what on the page is linked to. ref DRT 1 6630  Dave
141668 -     Buoncristiani cited problem on 990419. ref SDS 12 2601  On 990426
141669 -     Morris wanted a system to "prioritize" links. ref SDS 13 0558  On
141670 -     000504 Eric Armstrong found that opening links is confusing.
141671 -     ref SDS 77 1739
141672 -
141674 -           ..
141675 -          Intelligence May Lead to Knowledge to Solve World Problem
141676 -
141677 -          In one sense, Paul is submitting information, and this
141678 -          record strives to convert it into helpful "intelligence."
141679 -
141680 -          Paul's comment about having multiple windows open suggests a
141681 -          partial solution to the problem.
141682 -
141683 -          Seems like there are settings that control whether links open
141684 -          in the same or in multiple windows.  There is for the OS, but
141685 -          cannot find anything on this for Netscape and IE.  For
141686 -          example System Management (also called My Computer) has a
141687 -          Tools menu that controls opening directories in multiple or
141688 -          the same window.  Cannot find this for IE and Netscape.
141689 -
141690 -
141691 -
141692 -
1417 -

SUBJECTS
SDS Improvements, GUI
Internet, Web, HTML

160501 -  ..
160502 - Navigation Aids (Map) Can Enhance SDS on the Internet
160503 -
160504 - Paul sets out improvements or features he would like in the SDS
160505 - environment on the Internet...
160506 -
160507 -        [...below he proposes a solution. ref SDS 0 0035
160508 -
160509 -    •  ways to have meta-navigation information (threads I am
160510 -       following), ref DRT 1 5544,
160511 -
160512 -       Comment...
160513 -
160514 -       This is an important objective, if I understand Paul's point
160515 -       correctly, he is addressing the problem cited above. ref SDS 0
160516 -       0894  Everybody wants a "map" to navigate SDS records, as
160517 -       reported by Morris on 990426, ref SDS 13 1100, and 000427.
160518 -       ref SDS 14 8159
160519 -
160520 -       SDS supports the ability to think, remember and communicate in a
160521 -       number of ways which are not available on the web, and which
160522 -       might be considered "meta-navigation," but in any case have
160523 -       proven to be helpful....
160524 -
160525 -       1.  Description of the record provides orientation on subject
160526 -           and purpose.
160527 -
160528 -           Not sure if Paul has noticed that the date and record
160529 -           description are in the title bar at the top of the browser
160530 -           to provide orientation of sequence, per work on 990218.
160531 -           ref SDS 11 2972
160532 -
160533 -       2.  Contacts associated with the record do the same thing.
160534 -
160535 -       3.  Date and time of the record, per discussion of sequence on
160536 -           991014. ref SDS 19 5600
160537 -
160538 -       4.  Narrative in the record tells a story of cause and effect
160539 -           that is easier to remember than mere data and information,
160540 -           per review on 900303. ref SDS 1 3016
160541 -
160542 -       5.  Related records and documents, such as a letter, book, or
160543 -           other work product provide a rich array of pointers.
160544 -
160545 -       6.  Headings provide clues about the subject at hand, applying
160546 -           the concept of summary explained in POIMS. ref OF 1 8316
160547 -
160548 -       7.  Subjects assigned to one or more paragraphs - from 1 to 30
160549 -           or more provide structure to context and epistomology.
160550 -
160551 -    •  meta-hypertext (outlines and labeled trees/webs), rT 1
160552 -       1150,
160553 -
160554 -       Comment...
160555 -
160556 -       Just guessing, but may be part of points 1 - 6 above, and we are
160557 -       calling it something different, maybe "summary," "headings" and
160558 -       "organic subject structure," that provides both relational and
160559 -       hierarchical relationships.  Would be interesting to review this
160560 -       idea in more depth.
160561 -
160562 -       Possibly Paul could provide a link to an example, provide a
160563 -       mock up, and/or explain this requirement.
160564 -
160565 -
160566 -
1606 -

SUBJECTS
Map Needed for Linked Web Pages
Search Engine Needed for SDS on the Internet
Subject Search

180601 -     ..
180602 -    Search Capability for SDS on the Internet
180603 -
180604 -
180605 -    •  searchability (for say the word "Pointrel"), and, rT 1 2440
180606 -
180607 -       Comment...
180608 -
180609 -       This is a central feature of SDS using an organic subject
180610 -       structure, and other methods.  It is fairly complex per
180611 -       discussion with Morris on 970116. ref SDS 6 1732  Porting this
180612 -       method to the web was part of a proposed to NSF on 990615,
180613 -       ref SDS 18 3844, denied on 991213. ref SDS 20 0001
180614 -
180615 -       There is an argument that such capability is not needed since
180616 -       the purpose of the record on the Internet is to facilitate, yet
180617 -       maintain control, of communicating, in the same way one decides
180618 -       what to say, and what not to say, to people.  Thus, there is an
180619 -       inherent conflict with privacy and security objectives by
180620 -       empowering others to investigate another person's knowledge
180621 -       base.
180622 -
180623 -       Still, there seems to be a great interest in this feature, so it
180624 -       has commercial potential, per Morris' request on 000427 cited
180625 -       above. ref SDS 14 5624
180626 -
180627 -       We have to remember, that SDS records are not like looking up
180628 -       something in the encyclopedia where everything is intended for
180629 -       everybody.  With SDS we give people the power to create and
180630 -       maintain an encyclopedia of their lives and organizations, and
180631 -       to share what they wish to share, when and with whom they wish
180632 -       to share it, within the meaning of...
180633 -
180634 -
180635 -                    clear, concise, complete communication
180636 -
180637 -
180638 -       ...developed on 000630. ref SDS 5 1643
180639 -
180640 -       It may be possible to balance privacy, and sill give people a
180641 -       sense of searchability on that part of the record that is
180642 -       intended to be disclosed to them.
180643 -
180644 -       Actually, this is easily done with SDS already.
180645 -
180646 -       We download stuff and it becomes part of our record.  We don't
180647 -       try to download stuff people don't send us in order to maintain
180648 -       accountability for giving notice.  For example, Paul sent me a
180649 -       letter with certain information.  I do not have an overwhelming
180650 -       desire to search all of his letters.  I only want to search the
180651 -       letters and related information he directs to my attention. If I
180652 -       am given wider access, my liability for taking responsible
180653 -       action greatly expands, and I do not have time to review it all.
180654 -
180655 -    •  ways to "pivot" around a concept (i.e. see all related
180656 -       information to say "Pointrel" -- all pages that link to related
180657 -       documents, and all pages that it links to. For example, my
180658 -       product "StoryHarp", ref DRT 1 1056
180659 -
180660 -       <DIR>
180661 -       http://www.kurtz-fernhout.com/StoryHarp/screens.htm
180662 -       </DIR>
180663 -
180664 -       ...allows pivoting around a "node" in its browser window.)
180665 -
180667 -        ..
180668 -       Paul's Work Supports "Story" as Central to Learning
180669 -
180670 -       Briefly looked at Paul's website.  It shows powerful tools that
180671 -       may help navigate the SDS organic subject structure, among other
180672 -       things.
180673 -
180674 -       A big potential nexus between Paul's work and SDS is that both
180675 -       are geared toward the notion of "story" as a foundation to
180676 -       learning, reviewed on 900303. ref SDS 1 3016
180677 -
180678 -       SDS provides "pivot" capability in a lot of unique and helpful
180679 -       ways that are not available to people on the web, because the
180680 -       purpose of delivering "intelligence," is different from using
180681 -       SDS to lift the capacity to think, remember and communicate.
180682 -
180683 -       For marketing, would like to present SDS in the professional
180684 -       quality windows Paul's web site shows.  This would entail a
180685 -       deeper level of collaboration than seems to be contemplated by
180686 -       Paul's initial proposal today. ref SDS 0 0837
180687 -
180688 -           [On 000608 notified Paul about this idea. ref SDS 99 2220
180689 -
180690 - Paul further comments that many of the limitations he experiences
180691 - using SDS records on the Internet, per above, could be construed as
180692 - limitations of the HTML browser he is using, i.e., Netscape, not
180693 - Welchco, Communication Metrics, or SDS. ref DRT 1 5775
180694 -
180695 -       Comment...
180696 -
180697 -       See idea above about changing settings to open links in the same
180698 -       window. ref SDS 0 0852
180699 -
180700 -       The most helpful thing about Paul's letter is that he is aware
180701 -       of SDS and Communication Metrics, and seems comfortable using
180702 -       these in communications.
180703 -
180704 -
180705 -
180706 -
1808 -

SUBJECTS
Concepts Security and Privacy, SDS Records
SDS Features Security, Privacy
Privacy Suppress Record Text Segments from Publication on Web
Webmail, 980329
Webmail Reduces Errors
Web Mail Permits Correcting Mistakes

240901 -  ..
240902 - Privacy, Confidentiality, Security Need More Work in SDS
240903 - Email Improved by SDS Webmail
240904 -
240905 - Paul indicates that features like...
240906 -
240907 -       •  privacy and
240908 -
240909 -       •  email-hypertext integration/replication
240910 -
240911 - ...require changes to SDS. ref DRT 1 1968
240912 -
240913 -       Comment...
240914 -
240915 -       Privacy, security, confidentiality have been given consideration
240916 -       in SDS, but more is needed for some situations.
240917 -
240918 -       The problem of the message not getting through, however, dwarfs
240919 -       concern about the wrong people snooping around in the record.
240920 -       People with experience using SDS records can safely conclude
240921 -       that a lot of records need to be reviewed in order to get the
240922 -       picture, and getting only half or a quarter of the picture,
240923 -       which snooping tends to do, leads to incorrect understanding,
240924 -       and so is of no help.
240925 -
240926 -       With that understanding, we definitely want ways to step up
240927 -       privacy when desired.
240928 -
240929 -       Need example of what Paul has in mind about email-hypertext
240930 -       integration/replication.  What is going to be integrated and
240931 -       replicated and how will this improve the work?
240932 -
240933 -       Right now we can provide webmail that integrates correspondence
240934 -       into the context of Knowledge Space to provide...
240935 -
240936 -
240937 -                 clear, concise, complete communication
240938 -
240939 -
240940 -       ..., explained on 960620. ref SDS 5 1643  Would be very helpful
240941 -       if Paul can advance this objective.
240942 -
240943 -
240944 -
240945 -
2410 -

SUBJECTS
Fernhout, Paul, 000601
Open Source Advantages Enhancements by Many People
Map Needed to Maintain Focus
Original Docs Should Not Be Changed, 000609
Engineering Management
Traceability to Original Sources Metric Aligns People Through Communi
Align Avoid Rework Mistakes Subjects Discover all Factors
Original Work Preserved by Traceability to Sources
Accuracy Improved Audit Trail Original Sources

361201 -  ..
361202 - Proposal for Navigation, Interaction Tools for SDS on Internet
361203 -
361204 - Paul proposes to improve SDS presentation and searchability on the
361205 - web, and notes potential for snags in reaching agreement for a common
361206 - effort on issue of Intellectual Property (IP), which seems to be
361207 - related to the Open Source discussion.
361208 -
361209 - Paul proposes the following...
361210 -
361211 -    •  He downloads all the contact on Welchco.com using a site grabber
361212 -       program in Python. ref DRT 1 2200
361213 -
361214 -       Comment
361215 -
361216 -       Depending on the scope of any eventual project, the record
361217 -       could be provided to Paul directly.
361218 -       ..
361219 -       As well, it is helpful to develop a means for people to
361220 -       "grab" information from the web and integrate it into their own
361221 -       view of the world, where they can "think" about it with their
361222 -       own tools, which they control within the meaning of "knowledge
361223 -       management." That is how SDS is used now, and it may be what
361224 -       Paul has in mind, and so of course a project would need to
361225 -       create and test this capability.
361226 -
361227 -       Such an effort would be an "SDS" project.
361228 -
361229 -       Alternatively, we could leave SDS alone, and simply create an
361230 -       intermediate capability for only viewing and organizing the
361231 -       record, since not everyone has the time to perform knowledge
361232 -       management, per se, and also do real estate, law, medicine,
361233 -       science, manage a business, and so on.
361234 -
361235 -       This is a pretty big issue that people tend to rush by, because
361236 -       they have no experience doing KM day-to-day.  KM and in my
361237 -       parlance Communication Metrics is a new work discipline, that
361238 -       compliments accounting, marketing, engineering, facilities, law,
361239 -       operations, and so on.  We need one kind, or level, of special
361240 -       tool for "expert" practitioners, like CPM is a specialized tool
361241 -       for project management, and lessor tools for people who use and
361242 -       interact with work product of KM.
361243 -
361244 -       Paul seems to be thinking about a project to create intermediate
361245 -       support tools.
361246 -
361247 -    •  He creates a Python program that parses the HTML and puts it
361248 -       into a Pointrel data repository, complete with links modeling
361249 -       relationships. ref DRT 1 1152
361250 -
361251 -       Question
361252 -
361253 -           We leave the SDS record as is, so people can use it in that
361254 -           form, if desired.
361255 -
361256 -           Paul provides additional capability to process the record
361257 -           into an alternate format that provides solutions to the
361258 -           problems he discusses above???
361259 -
361260 -    •  He creates a browser in Python that supports search,
361261 -       meta-information, limited (easily defeatable) privacy, and
361262 -       pivoting over that knowledgebase. ref DRT 1 3744
361263 -
361264 -       Question
361265 -
361266 -           Is this browser transparent to the User in the sense that
361267 -           it is part of existing ways and means of using stuff on the
361268 -           web, generally Netscape and IE, or is it something people
361269 -           have to call specifically to implement this new capability?
361270 -
361271 -           I guess I am asking if there is an added step for this that
361272 -           might reduce the desire to use the system, relative to
361273 -           other work people are doing?
361274 -
361275 -           Alternatively, Paul may have in mind creating a new standard
361276 -           for browsers which provide sufficient self-evident added
361277 -           value that people would move to the new tool??
361278 -
361279 -    •  [Optional] I create Python tools to allow adding new materials
361280 -       and exporting repository materials to HTML. ref DRT 1 6175
361281 -
361282 -       Question
361283 -
361284 -           Need explanation of a scenario where this might be applied.
361285 -
361286 -           Suppose someone encounters this record on the web.
361287 -
361288 -           One idea Paul may have in mind is the ability to grab up
361289 -           this record and insert comments, as I am doing now, which
361290 -           then makes it the users record, not the originators, and it
361291 -           can be linked to the originator, both ways, if desired.
361292 -
361293 -           This sounds useful, but people have to realize that the
361294 -           environment gets very complicated very quickly.  We need to
361295 -           think through how to avoid overwhelming span of attention.
361296 -
361297 -    •  [Optional] I integrate this with a mail reader and sender.
361298 -       ref DRT 1 0950
361299 -
361300 -       Question
361301 -
361302 -           Need explanation of a scenario where this might be applied.
361303 -
361304 -    •  [Optional] I modify Zope to serve Welchco content from a
361305 -       repository [not static HTML], ref DRT 1 1740
361306 -
361307 -       Question
361308 -
361309 -           Need explanation of a scenario where this might be applied.
361310 -
361311 -    •  The content remains yours, and is either returned to you in a
361312 -       Pointrel repository or better as a set of Python tools you can
361313 -       use to build your own repository from your site. [Optional:
361314 -       Maybe you let me keep a copy for additional local testing, not
361315 -       to be redistributed without your permission.], ref DRT 1 2982
361316 -
361317 -       Comment
361318 -
361319 -           I do not understand what Paul has in mind on this point.
361320 -
361322 -            ..
361323 -           Original Work Unchanged, Use Traceability Original Sources
361324 -           Collaboration Preserves Original Work, Traceability
361325 -           Dynamic KM System Supports Thinking, Doing, Collaboration
361326 -
361327 -           Ultimately, the purpose of the record is to guide action.
361328 -
361329 -           Just thinking out loud, I write up a record in order to
361330 -           understand this or that, and develop planning for doing
361331 -           things.  I send parts of the record to different people to
361332 -           get them to do things, and hear back from them about their
361333 -           ideas and concerns.  They may use the record I send as part
361334 -           of something else they are thinking about, and/or send me
361335 -           something that includes some of what I sent them, and part
361336 -           of other things they received from other people, to guide my
361337 -           conduct, and/or they may combine my communication with stuff
361338 -           from others with the aim of influencing 3rd parties to do
361339 -           unrelated stuff.  But, everybody is not interested, nor
361340 -           needs to know about everything everybody else is up to.
361341 -
361342 -           We need to think this through carefully.
361343 -
361344 -             [On 000609 SRI team for DKR proposes using Wiki to change
361345 -             original work, conflicts with engineering management.
361346 -             ref SDS A0 1008
361347 -
361348 -             [On 000703 Morris objects to changing original work.
361349 -             ref SDS A2 6030
361350 -
361351 -    •  The resulting Python code is put under the same license as
361352 -       Pointrel is now (X/MIT) [or maybe instead GPL or LGPL.].
361353 -       ref DRT 1 2922
361354 -          ..
361355 -       Comment
361356 -
361357 -           This may work out well, if I am understanding correctly that
361358 -           the original code for generating the record as the core
361359 -           engine of KM and Enterprise Management is SDS.
361360 -
361361 -           SDS entails a counterintuitive process that not everybody
361362 -           grasps.
361363 -
361364 -           What Paul is proposing is a means for people to use the
361365 -           record in ways they do grasp, i.e., I see a record, I
361366 -           comment on a record, as with current email, but with added
361367 -           ability to create links.
361368 -
361369 -    •  <0264 So, you share your experience doing Knowledge Management
361370 -       with hypertext, especially the great example you have produced
361371 -       with Welchco, and I share my experience with data repositories
361372 -       and GUIs -- and at the end there is an open source result.
361373 -       ref DRT 1 1770
361374 -
361375 -       Comment
361376 -
361377 -          This seems doable, possibly providing a path for wider
361378 -          cooperation.
361379 -
361380 -          SDS is proprietary, but offers a development path for useful
361381 -          open source efforts, such as Paul proposes for SDS work
361382 -          product on the web, as set out on 000503. ref SDS 75 6903 In
361383 -          the same way that Paul uses a computer, car, desk and other
361384 -          tools to support open source development, SDS is another tool
361385 -          he can use for creating open source programs.
361386 -
361387 -          Additionally, Paul might be willing to participate in SDS as
361388 -          an owner and developer to enhance the full range of tools
361389 -          needed for effective knowledge management.
361390 -
361391 - ..
361392 - Summarizing...
361393 -
361394 -       First impression and preliminary analysis suggests that Paul's
361395 -       proposal leads toward the Enterprise Management model formulated
361396 -       on 990427, ref SDS 15 7503, and described in the proposal to
361397 -       NSF, ref OF 6 0001, on 990427, ref SDS 18 3844, using SDS as the
361398 -       engine to generate knowledge on the web, and Paul's tools for
361399 -       people to more easily apply the intelligence.
361400 -
361401 -       If Pointrel renders SDS content in a form that is easier to use
361402 -       and adds utility, per search capability cited above, ref SDS 0
361403 -       1443, this would increase demand for SDS to generate content,
361404 -       as the core engine of knowledge management.
361405 -
361406 -       Per above, it may align with ideas discussed with Jack Park on
361407 -       000503. ref SDS 75 6903
361408 -
361409 -       The reason this might be a good idea is because the tools Paul
361410 -       seems to be proposing reduce the need to teach everybody the
361411 -       concepts of POIMS and the complex functions of SDS that are
361412 -       counterintuitive, and so hard to understand, in order for them
361413 -       to benefit from "intelligence."  We can teach a few people, and
361414 -       everybody else can keep working in their normal manner, but get
361415 -       better results.  It provides a partial solution to the diligence
361416 -       issue, where people simply are not inclined nor in many cases do
361417 -       have the aptitude for using SDS.  This gets us started solving
361418 -       those world problems Doug is talking about, by improving
361419 -       productivity of a lot of people.
361420 -
361421 -       In the same way that a car leverages muscle power to help a lot
361422 -       of people, we have found that a little intelligence added to
361423 -       management everyday helps a lot of people think, rememeber and
361424 -       communicate better which reduces mistakes and enhances discovery
361425 -       of opportunities that are otherwise overlooked.
361426 -
361428 -  ..
361429 -
361430 - Paul cites negative forces against the proposal...
361431 -
361432 -    •  It undermines your proprietary interest in the structure of your
361433 -       site and related tools. ref DRT 1 6305
361434 -
361435 -       Comment
361436 -
361437 -       Need explanation of how propritary interest would be affected
361438 -       in the record.
361439 -       ..
361440 -       This concern helps focus on what Paul really has in mind.
361441 -       I may not be understanding it correctly, because, off-hand, I do
361442 -       not see the problem he suggests.
361443 -
361444 -       Say Rod sends Paul a letter on the web, and cites an SDS record
361445 -       or two for clarification.  Paul grabs the letter and any records
361446 -       he wishes to keep, as a record of what he saw and did, using his
361447 -       Pointrel tool, including adding comments.  Rod's record remains
361448 -       untouched, and Paul now has a record in his system with his
361449 -       comments.  He sends Rod a reply, referencing Rod's original
361450 -       record and links to his copy of the record with his comments.
361451 -       Rod's record is unchaged on his website (filing cabinet), but he
361452 -       now has Paul's comments, which can be analysed in a new record
361453 -       linked back to Paul's comments, if Rod wishes, or he may not do
361454 -       that in the same way people decide every day whether to do
361455 -       something about information they see and hear or move on and
361456 -       change the channel.
361457 -       ..
361458 -       One thing we want to avoid is reaching for the perfect
361459 -       solution.
361460 -
361461 -       It will always be elusive, just beyond reach.  We want to
361462 -       improve by an order of magnitude current work practice, which is
361463 -       exemplified by Eric Armstrong's letter today, saying he could
361464 -       not comment on the POIMS paper because he printed it, prepared
361465 -       handwritten comments, and then left it in his car or lost it.
361466 -       ref SDS 95 6035  We want to improve that scenario to help Eric
361467 -       and others, and we have a way to do it that nobody else has
361468 -       discovered, and which works well.
361469 -
361470 -    •  It creates more copyright & licensing issues & liability in your
361471 -       redistributing the web content. ref DRT 1 7844
361472 -
361473 -       Comment
361474 -
361475 -       Isn't this mainly an issue of attribution, discussed in the
361476 -       record on 000227? ref SDS 48 0987
361477 -
361478 -       There is also an issue of privacy and security.
361479 -
361480 -       Probably need legal advice, as Paul has advocated, for example
361481 -       in his letter, ref DRP 1 0001 on 000203. ref SDS 29 0001
361482 -
361483 -    •  It would take some of your time. ref DRT 1 0988
361484 -
361485 -       Comment
361486 -
361487 -       Assuming these improvements are worthwhile, this time will be
361488 -       invested to improve earnings and save time, possibly solve a
361489 -       world problem, which would be time well spent.
361490 -
361491 -    •  <0837 Collaborations can go sour. ref DRT 1 2332
361492 -
361493 -       Comment
361494 -
361495 -       Lack of collaboration may prevent a solution, so this is a toss
361496 -       up.
361497 -
361498 -       Further, Paul seems to be proposing an implementation
361499 -       independent of SDS, other than to process the record on the
361500 -       Internet, so there may not need to be a lot of collaboration,
361501 -       per se.
361502 -
361503 -       On the other hand, it would be enormously beneficial to go ahead
361504 -       and develop improvements to SDS, per above, ref SDS 0 4071, that
361505 -       would require a lot of collaboration which could be pretty
361506 -       painful in unlocking the secrets of KM enough for Paul to get
361507 -       going, as has occurred with Morris, reported on 920215.
361508 -       ref SDS 2 5820
361509 -
361511 -  ..
361512 -
361513 - Friendly forces favoring the proposal...
361514 -
361515 -    •  It would be nice to see some open source KM code, even if it
361516 -       isn't everything an OHS could be. ref DRT 1 2408
361517 -
361518 -       Comment
361519 -
361520 -       KM would be nice to have from any source, since it does not
361521 -       otherwise exist, and is not on the drawing boards anywhere, per
361522 -       meeting at SRI on 000330, ref SDS 63 0713, and review on 000106.
361523 -       ref SDS 22 0877  The threshold question is what does it take to
361524 -       produce it by any means, not by a particular means.
361525 -
361526 -       See caution above about reaching too far, too fast. ref SDS 0
361527 -       4074
361528 -
361529 -       The big issue is to add intelligence to management, which right
361530 -       now is overwhelmed by information overload.  This entails giving
361531 -       people a much stronger form of knowledge creation than is
361532 -       available with present use of alphabet technology, applied with
361533 -       pen and paper, printing press and wordprocessing, which can only
361534 -       produce information.  These technologies rely on the human mind
361535 -       to create the actual knowledge.  SDS provides a way to aid human
361536 -       thinking that produces knowledge by integrating time and
361537 -       information with the structure of spreadsheet technology.  This
361538 -       method, i.e., a spreadsheet for knowledge, directly enhances the
361539 -       qualify of work, which can help solve world problems better than
361540 -       existing alphabet technology.
361541 -
361542 -       It also provides a development path for a wider range of people
361543 -       to learn about the plan, perform, report "intelligence" process
361544 -       who can then develop add on capabilities, as Paul proposes
361545 -       today, that will provide bells and whistles people dream about
361546 -       for an OHS/DKR.
361547 -
361548 -    •  You might have some better open-source tools for doing your
361549 -       consulting. ref DRT 1 4248
361550 -
361551 -       Comment
361552 -
361553 -       Per your next point, a Pointrel add-on to provide command and
361554 -       control of "intelligence" on the Internet would help sell
361555 -       consulting time, and demonstrate the value of SDS.
361556 -
361557 -       In my particular case, I need to begin thinking about other ways
361558 -       to use SDS for a revenu stream.  Generating "intelligence" takes
361559 -       time and energy of young people 30 - 50.  I am at the end of
361560 -       that cycle.  We need to begin training others to do this work,
361561 -       as a co-evolution process that Doug Engelbart advocates, but so
361562 -       far has not acted on any of the notices submitted urging support
361563 -       for this essential next step in the "revolution."
361564 -
361565 -    •  I would have a good example of using Pointrel to show people.
361566 -       ref DRT 1 5658
361567 -
361568 -       Comment
361569 -
361570 -       Theoretically, Paul and others would also have a powerful tool
361571 -       for improving their work day-to-day.
361572 -
361574 -  ..
361575 -
361576 - Paul requests ideas on what makes sense.
361577 - ref DRT 1 0936
361578 -
361579 -    Generally, Paul's proposal aligns with ideas discussed with Jack
361580 -    Park on 000503, ref SDS 75 6860, where Rod is willing to share
361581 -    participation in SDS with others, e.g., certainly Morris, but also
361582 -    Jack, Eric, and now Paul.
361583 -
361584 -    Subsequently, Jack is pausing over the issue of open source, and
361585 -    Eric does not see merit in SDS and POIMS, per meeting with Morris
361586 -    at Intel on 000517. ref SDS 88 0825
361587 -
361588 -    Paul seems to reflect Jack's sense about the potential for SDS,
361589 -    so it remains to be seen whether a constructive business
361590 -    relationship can be fashioned to accomodate diverse agendas.
361591 -
361592 -
361593 -
361594 -
361595 -
361596 -
361597 -
361598 -
3616 -
3617 -