CONTACTS 
0201 - Science Applications                 619 546 6000
020101 - Mr. Roy Roebuck

SUBJECTS
Roebuck, Roy, 990621
Colloquium Unfinished Revolution, 000106
Roebuck's Gem System Oneness
Context Management

0706 -    ..
0707 - Summary/Objective
0708 -
070801 - Follow up ref SDS 14 0000, ref SDS 13 0000.
070802 -
070803 - Roy Roebuck submitted a letter to the Colloquium, but it is not
070804 - readable.  Sent a response letting him know and requesting further
070805 - submission. ref SDS 0 0843  Notified about results of NSF proposal.
070806 - Benay Dara-Abrams suggesting Augment/NLS can support the Colloquium,
070807 - ref SDS 0 0738, and he recommends strategic planning.  Jeff Miller
070808 - concurs on need for strategic planning. ref SDS 0 8960  Jeff proposes
070809 - starting with an effort to improve document management, ref SDS 0
070810 - 3867, also submits ideas on using XML, which aligns with Roy's ideas
070811 - last year for the NSF project. Eric Armstrong concurs with using XML
070812 - as a starting point, and expects to develop further project planning.
070813 - He reports XML standards are not well developed and asks for original
070814 - sources on this work. ref SDS 0 0612  Jon Winters proposes time based
070815 - management, that reflects the SDS design.  Jon says version control
070816 - can use write once data storage based on research at NASA that shows
070817 - molecular nano technology is a strong possibility. ref SDS 0 4961
070818 - Mike Taylor and Tanya Jones review project objectives and scope,
070819 - suggesting a DKR design must support a process that has the power and
070820 - flexibility to address large and small problems. ref SDS 0 4449
070821 -
070822 -
070823 -
070824 -
0709 -
0710 -
0711 - Progress
0712 -
071201 -  ..
071202 - Roy's DKR Planning and Development Ideas Need Re-submission
071203 -
071204 - Roy sent a letter to Doug's colloquium, but it was unreadable,
071205 - evidently in some kind of code.
071206 -
071207 - I sent him a letter, ref DIT 1 0001, explaining the problem with his
071208 - submission, and asking for a correction.
071209 -
071210 -      [On 000125 Roy resubmitted his two letters. ref SDS 21 2850 and
071211 -      also ref SDS 21 4449]
071212 -
071213 - Also notified Roy that NSF rejected the proposal on Communication
071214 - Metrics. ref SDS 18 0001
071215 -
071216 -      [On 001112 another follow up letter to Roy. ref SDS 34 0001
071217 -
071218 - Asked Roy for an update on his letter, ref DRP 2 0001, received on
071219 - 990621, commenting favorably on the NSF proposal, and indicating he
071220 - was reviewing the approach to take with his KM ideas, ref SDS 14 0001,
071221 - following up his submission on 990427 of an initial NSF proposal
071222 - outline. ref SDS 11 3360
071223 -
071224 - Roy submitted a bunch of new stuff, later in the evening, but it,
071225 - too, was not readable.  Sent him another note saying it is not coming
071226 - through.
071227 -
071228 - Eric Armstrong, also, sent a letter to Roy explaining no one can read
071229 - Roy's submission to Colloquium. ref DRT 1 0001
071230 - ..
071231 - I sent a reply to Eric, ref DIT 2 0001, that relates Roy's ideas
071232 - on Context Management for an open source Enterprise Management
071233 - capability modeled on the Doug's DKR idea, per the record on 990427.
071234 - ref SDS 11 3360, that reflects analysis of Eric's initial DKR outline
071235 - in the record on 000120. ref SDS 20 1225
071236 -
071237 - Eric's response to Jeff Miller did not cite Roy's ideas. but mentions
071238 - XML, ref DRT 4 3976, which is part of Roy's NSF proposal, reported on
071239 - 990427, per below. ref SDS 0 3551
071240 -
071241 -     [On 000125 Bill Bearden commented favorably on Roy's proposals for
071242 -     Context Management. ref SDS 21 2850]
071243 -
071244 -
071245 -
071246 -
071247 -
071248 -
0713 -

SUBJECTS
Augment/NLS, 000124

0904 -
090401 -  ..
090402 - Augment NSL Proposed to Support DKR Design Development
090403 -
090404 - Follow up ref SDS 20 2688, ref SDS 19 0786.
090405 -
090406 - Received ref DRT 2 0001 from Jeff Miller proposing ideas to begin
090407 - thinking about specific design issues.
090408 -
090409 - Jeff cites a letter from Benay Dara-Abrams who suggests...
090410 -
090411 -       ...make Augment/NLS available in some form for the group to use.
090412 -
090413 -       ...it would help us build our DKR if we had the right tools,
090414 -       ref DRT 2 2256
090415 -
090416 -         [On 000302 Eugene Kim suggests using available tools to gain
090417 -         experience for building a DKR. ref SDS 28 0896
090418 -
090419 -         [On 000326 Doug Engelbart proposed that DKR team meeting at
090420 -         SRI use the DKR project as a prototype for KM to learn how to
090421 -         build a DKR. ref SDS 31 5972
090422 -
090423 - Jeff does not comment on Augment/NSL
090424 -
090425 -     [On 000125 Eric Armstrong includes Augment NSL in the outline for
090426 -     Document Management, and requests requirements. ref SDS 21 0738]
090427 -
090428 -
090429 - ..
090430 - It would help to get from Benay an example or two of how this
090431 - capability would be applied to support DKR design effort.
090432 -
090433 -     [On 000407 listed as possible agenda item for project meetings.
090434 -     ref SDS 33 4320
090435 -
090436 -
090437 -
090438 -
090439 -
0905 -

SUBJECTS
Objectives Knowledge Space
Planning, Scope, Objecitves, Requirements
Assignments
Collaboration

1507 -
150701 -  ..
150702 - Objectives and Plan of Action Needed
150703 -
150704 - Jeff's letter quotes Benay further suggesting in the prior letter...
150705 -
150706 -       We have lots of ideas but I think we need to move into a
150707 -       concrete plan of action. Perhaps, we need to set some objectives
150708 -       for what we'd like to accomplish during the colloquium in terms
150709 -       of building the DKR. ref DRT 2 4355
150710 -
150711 - Jeff concurs. ref DRT 2 7708   Below, Mike Taylor and Tanya Jones
150712 - review project objectives and scope. ref SDS 0 4449
150713 -
150714 - This aligns with analysis of Eric Armstrong's initial outline, calling
150715 - for planning on 000120, ref SDS 20 0848
150716 -
150717 -     [On 000125 Dick Karpinski suggests WBS methods. ref SDS 21 8960]
150718 -
150719 -     [On 000324 Eugene Kim assigned to develop plan. ref SDS 30 6036
150720 -
150721 - Previously, on 990427 analysis if NSF project showed need for planning
150722 - and organization on a wide range of issues. ref SDS 11 3422
150723 - ..
150724 - Eric responds to Jeff's letter, reporting plans to write up a
150725 - preliminary version tonight. ref DRT 4 2957
150726 -
150727 -     [On 000127 John Deneen provides suggestions for specific tools to
150728 -     investigate toward a system design framework. ref SDS 22 8960]
150729 -
150730 - It is not clear if this is specific XML code planning, or whether it
150731 - is the project planning requested by Benay and Jeff.
150732 -
150733 -
150734 -  ..
150735 - Not Enough Time for Everyone to Investigate Everything
150736 - Planning Team Define Objectives, Scope, WBS, Assignments
150737 -
150738 - Jeff reports having half answers which lead to many more questions. If
150739 - there were twice as many hours in a day it would still not be possible
150740 - to read all that is necessary. ref DRT 2 6557
150741 -
150742 - Jeff suggests a DKR with summaries and collaboration with others to
150743 - solve the problem of limited time by dividing the project into
150744 - managable work packages.
150745 -
150746 -     [On 000125 Dick Karpinski proposes "Idea Farm" as element of DKR
150747 -     which may support DKR development. ref SDS 21 0582]
150748 -
150749 - Limited time is a major design objective for an effective DKR which is
150750 - addressed in Communication Metrics with SDS technology that integrates
150751 - time and information, ref OF 1 1298, also, explained in the proposal
150752 - to NSF. ref OF 3 7802  However, technology alone is not enough to save
150753 - time for key people like Jeff.  The U.S. Army Corps of Engineers
150754 - reported that a new player is needed, a Communication Manager, cited
150755 - in the NWO... ref OF 2 6369
150756 -
150757 - An organizing scheme and method of tracking action items can support
150758 - this process.
150759 -
150760 - Might Action Item tracking be a helpful aspect of a DKR?
150761 -
150762 - Some level of leadership for making assignments or facilitating
150763 - collaboration could be helpful, as proposed to Eric Armstrong on
150764 - 000120. ref SDS 20 0848
150765 -
150766 - Eric Armstrong's response to Jeff's letter reports plans to write up a
150767 - preliminary version tonight, and notes that several more iterations
150768 - will be required. ref DRT 4 2957
150769 -
150770 -
150771 -
150772 -
150773 -
1508 -

SUBJECTS
Documents (DKR) 000124
Document Management Systems

2305 -
230501 -  ..
230502 - DKR Design for Document Management
230503 -
230504 - Jeff proposes taking a specific document and...
230505 -
230506 -         comparing possible methods of encoding, ref SDS 0 3551
230507 -         storage
230508 -         searching
230509 -         etc?
230510 -
230511 - ...ref DRT 2 5293
230512 -
230513 -        [below, he proposes using XML encoding. ref SDS 0 3551]
230514 -
230515 -     It might be useful to define objectives and parameters for each
230516 -     criteria.
230517 - ..
230518 - Jeff further suggests referring to specific points...
230519 -
230520 -         paragraphs
230521 -         lines
230522 -         sentences
230523 -         words
230524 -
230525 -         annotating the document,
230526 -         versioning,
230527 -         summarisation,
230528 -         etc?
230529 -
230530 - ...ref DRT 2 1813
230531 -
230532 - Jeff asks for a list of features we can test against to see if we meet
230533 - all the requirements for enhancing document management. ref DRT 2 2508
230534 -
230535 -  ..
230536 - Eric Armstrong's response cites's Jeff's ideas, ref DRT 4 0001, and
230537 - reports plans to write up a preliminary version tonight, noting
230538 - several more iterations will be required. ref DRT 4 2957
230539 -
230540 -      [On 000125 Eric submits outline. ref SDS 21 3867]
230541 -
230542 -      [On 000129 Eric submits design plan for XML editor. ref SDS 23
230543 -      3383]
230544 -
230545 -      [On 000219 Eric identifies 5 authoring functions. ref SDS 27 4892
230546 -
230547 -      [On 000406 Eric presents at team meeting progress on setting
230548 -      requirements for OHS Editor. ref SDS 32 0375
230549 -
230550 -      [On 000407 listed as possible agenda item for project team
230551 -      meetings. ref SDS 33 5938
230552 -
230553 - On 000120 set out initial questions for goals and guiding design of a
230554 - DKR, with respect to the meaning of "knowledge" and "intelligence."
230555 - ref SDS 20 2688 and ref SDS 20 3002
230556 -
230557 - ..
230558 - Additional features that might help document management...
230559 - 
230560 -     [On 000210 reviewed Eric's detailed design for document
230561 -     management. ref SDS 25 2993]
230562 -
230563 -     [On 000219 Eric's scope for authoring tools do not address any of
230564 -     these issues. ref SDS 27 4892]
230565 -
230566 -     [On 000407 listed as possible agenda item for project team
230567 -     meetings. ref SDS 33 5938
230568 -
230569 -         Definition
230570 -
230571 -           What is a "document"?  How does it relate to a continuous
230572 -           information stream?
230573 -
230574 -           [On 000212 Eric suggested these may be different.
230575 -           ref SDS 26 9790
230576 -
230577 -         Ownership
230578 -
230579 -           Who owns a document?
230580 -
230581 -         Location scheme in Knowledge Space
230582 -
230583 -           What rules govern how and where a document exists?
230584 -
230585 -         Identification
230586 -
230587 -           •  Unique Identification
230588 -           •  Description
230589 -           •  Type
230590 -           •  Subjects
230591 -           •  Author
230592 -           •  Title
230593 -           •  Addressee
230594 -           •  Date Time
230595 -
230596 -         Control
230597 -
230598 -           •  received
230599 -           •  issued
230600 -           •  pending response
230601 -           •  responded
230602 -           •  Anchors for Linking
230603 -
230604 -         Integration, Alignment and Linking
230605 -
230606 -           How are documents integrated with personal and
230607 -           organizational experience?  How do we capture our thinking
230608 -           about documents, generate controllable action items flowing
230609 -           from documents, actions taken as a result of information in
230610 -           documents, as well as what was left out, and thinking as a
230611 -           consequence of actions based on documents, cited in POIMS as
230612 -           critical management criteria? ref OF 1 0859
230613 -
230614 -           Communication Metrics calls these issues "understanding" and
230615 -           "follow up," cited in the record on 000120. ref SDS 20 2340
230616 -
230617 -           [On 000208 submitted ideas on this to Eric Armstrong
230618 -           answering his request for ideas about the core of knowledge
230619 -           management. ref SDS 24 4905
230620 -
230621 -           [On 000212 Eric Armstrong submitted a letter to the
230622 -           Colloquium offering an "innovation" to manage information
230623 -           without "documents" being the central focus. ref SDS 26 9790
230624 -           and ref SDS 26 1682
230625 -
230626 -
230627 -
230628 -
230629 -
2307 -
2308 -

SUBJECTS
XML Encoding, 001024
XML Editor

2805 -
280501 -  ..
280502 - XML May Provide Effective Method of Encoding
280503 - Encoding Using XML - Are Sub-interpreters Needed?
280504 -
280505 - Jeff leans toward XML encoding. ref DRT 2 3680
280506 -
280507 - On 990314 Roy Roebuck proposed XML for SDS, ref SDS 10 0406, based on
280508 - an explanation and web site for XML submitted on 990301. ref SDS 8
280509 - 9528  On 990225 XML was initially cited. ref SDS 6 8895
280510 -
280511 - Morris was asked about XML on 990227, ref SDS 7 2967  On 990301 there
280512 - are a series of questions still pending on using XML for SDS.
280513 - ref SDS 9 0773
280514 -
280515 - Today, Jeff notes...
280516 -
280517 -     ...one of the main problems once the data has been retrieved is to
280518 -     present/display it in a recognizable form to the user. Do we need
280519 -     (sub-)interpreters for every use of xml? Or, can we encode
280520 -     presentation infomation with, by reference, the document. The
280521 -     emerging uses of xml present us with the realization that
280522 -     extensible also has to apply to the viewing mechanism. ref DRT 2
280523 -     0544
280524 -
280525 -     Taking a quick glance at cml...
280526 -
280527 -     http://www.xml-cml.org/
280528 -
280529 -     ...it seems that they rely on java to interprete and display cml.
280530 -     This is an improvement over the mess of plug-ins that could have
280531 -     been relied upon, but is there a method that exists or that could
280532 -     be developed that does not rely on executable code? ref DRT 2 1160
280533 -
280534 - Jeff reports possible examples...
280535 -
280536 -     Annotated XML Specification, ref DRT 2 3000
280537 -
280538 -
280539 -     http://www.xml.com/xml/pub/axml/axmlintro.html
280540 -
280541 -
280542 -     The DocBook homepage
280543 -
280544 -
280545 -     http://www.docbook.org/
280546 -
280547 - ..
280548 - Eric Armstrong's response cites's Jeff's ideas, ref DRT 4 0001,
280549 - and makes following points on XML...
280550 -
280551 -       2.  XML does indeed seem like a good starting point. Apparently
280552 -           early versions of the XML spec were intended for this
280553 -           purpose, but the end result was constrained. We'd sure love
280554 -           to know what the early spec looked like. ref DRT 4 3976
280555 -
280556 -       3.  Unfortunately, the Annotated XML Spec is not a spec for
280557 -           capturing annotations in XML, but rather an annotated
280558 -           version of the XML spec. Interestingly, the annotations were
280559 -           captured in an XML document, using links to the spec. A Java
280560 -           program then broke up that document into a multitude of
280561 -           annonations, and inserted links to them into the XML spec.
280562 -           ref DRT 4 5346
280563 - ..
280564 - It would be helpful to get a general explanation of what would
280565 - be "started" by using XML, as Eric suggests. ref SDS 0 0612
280566 -
280567 -     [On 000125 Roy Roebuck reports his GEM knowledge management
280568 -     capability is enabled by XML. ref SDS 21 3551]
280569 -
280570 -     [On 000129 Eric submits details on using XML. ref SDS 23 0957]
280571 -
280572 -     [On 000305 Xanadu claims to solve limitations of XML. ref SDS 29
280573 -     1188]
280574 -
280575 -     [On 000406 Eric made detailed presentation to team meeting, but
280576 -     did not explain how XML is expected to improve present practice,
280577 -     and how that will solve a world problem. ref SDS 32 0375
280578 -
280579 -     [On 000407 listed as agenda item for project meetings. ref SDS 33
280580 -     0300
280581 -
280582 - This record does not indicate how XML would support SDS, per questions
280583 - to Morris on 990301. ref SDS 9 0773
280584 -
280585 - Eric's response to Jeff did not cite Roy's ideas disclosed in my
280586 - letter to Eric, ref DIT 2 0001, per above. ref SDS 0 6552
280587 -
280588 -
280589 -
280590 -
2806 -

SUBJECTS
Versioning Control
Disk Storage & Backup
Nano Technology

3506 -
350601 -  ..
350602 - Versioning Supported by Write Once Molecular Nano Technology at NASA
350603 - Time Enabled Hypertext for Version Control
350604 -
350605 - A letter from Jon Winters reports digital storage will continue to
350606 - increase, ref DRT 5 0001, becoming even less of a limitation in the
350607 - period ahead, based on an article published by the Journal of British
350608 - Interplanetary Society ing 1997, explaining research at NASA...
350609 -
350610 -
350611 -     http://www.nas.nasa.gov/Groups/Nanotechnology/publications/publications/1997/applications/
350612 -
350613 -
350614 - ...which has the title...
350615 -
350616 -
350617 -           NASA applications of molecular nanotechnology
350618 -
350619 -
350620 - The section titled Data Storage on Molecular Tape, describes a DNA
350621 - enzyme capability for data storage. ref OF 5 0170   No specific values
350622 - are presented for this method. The next section titled Data Storage on
350623 - Diamond, reports a study and proposes that if write-once data could be
350624 - stored this way, capacity would nearly double current DVD technology.
350625 - ref OF 5 0200
350626 - ..
350627 - Jon argues in his letter today that these new capabilities
350628 - warrant consideration for adopting a "write once" system of data
350629 - storage for version control.  Every time a document is saved a new
350630 - time-stamped copy is saved. Time is used to organize the life of the
350631 - document. Like us, the document evolves over time. ref DRT 5 2442
350632 -
350633 -     [On 000125 Eric Armstrong supports this idea. ref SDS 21 4961]
350634 -
350635 -     [On 000212 Eric proposes innovation to improve paradigm of
350636 -     knowledge as "documents." ref SDS 26 9790]
350637 -
350638 - This criteria reflects the core concept of the SDS design that is date
350639 - identified to reflect human reasoning based on chronology, as reported
350640 - on 991014. ref SDS 17 5600  Previously, on 900303 Campbell explains
350641 - that human cognition is based on experience. ref SDS 1 3002
350642 -
350643 - Adding "versioning" to maintain the evolution of changes is helpful,
350644 - within limits, particularly when the record is distributed to others.
350645 -
350646 - The implied notion that any resource is unlimited and so requires no
350647 - consideration for consumption seems over broad.
350648 - ..
350649 - If many versions of minor changes are maintained, a huge problem
350650 - of managing the volume emerges.  Some method of user control might be
350651 - developed.  It might be possible to trigger version control only when
350652 - a document is published, emulating the concept of public speech and
350653 - private thoughts.
350654 -
350655 - Jon points to a mock-up of what a "time enabled" web browser might
350656 - look like...
350657 -
350658 -
350659 -     http://obscura.obscurasite.com/unrev/images/time-enabled-browser.jpg
350660 -
350661 -
350662 - ...that contains some of the notes for session 3 of the Colloquium.
350663 - The bottom right corner a of the image shows time/date stamp.
350664 - ref DRT 5 1813
350665 -
350666 - It might be useful to have available what parts of a document have
350667 - been changed, to reduce the burden of review.
350668 -
350669 - Actually, interesting issues arise.  Suppose we have a 100MB set of
350670 - specs and change the title to italic, or move the date from the left
350671 - margin to the right margin.  Then the boss says to change things back.
350672 - Then the boss has a change of mind, and so on.  This could easily
350673 - consume a gig in just a few minutes.  Moreover, just random or
350674 - "nervouos" saving that has no changes, or we add some blank lines,
350675 - save it, then delete the lines.
350676 -
350677 -     [On 000125 Eric Armstrong discusses application that may address
350678 -     these questions. ref SDS 21 1053]
350679 -
350680 -
350681 -
350682 -
350683 -
350684 -
3507 -

SUBJECTS
Objectives, Collective IQ
Solve Problems
Global Problems Too Vast Lack Focus
ABC Improvement Model

3907 -
390701 -  ..
390702 - DKR Augment Capabilities Compliment Market Forces
390703 -
390704 - Tanya Jones submits a letter, ref DRT 3 0001, clarifying objectives of
390705 - the Colloquium in response to a letter from Mike Taylor commenting on
390706 - the broad sweep of the presentation that intends to address macro or
390707 - global (UN level) problems.
390708 -
390709 - Mike perceives that the goal to improve human capabilities is being
390710 - combined with prescriptions for solving social problems, that may
390711 - tend toward political agendas.
390712 -
390713 - This issue was reviewed on 000120, ref SDS 20 2808, in relation to a
390714 - similar inquiry by John Werneken. ref SDS 20 5110
390715 -
390716 - It is another way of saying we need strategic planning discussed
390717 - above. ref SDS 0 8960
390718 - ..
390719 - Tanya points out Bootstrap Institute's mission (as she reads it)
390720 - includes examining and improving ability to solve all problems. She
390721 - sees Doug applying his [ABC problem solving] models to problems large
390722 - and small: from the simple interfacing with data to the larger social
390723 - issues. ref DRT 3 2000
390724 -
390725 - ABC problem solving method is reviewed on 991222. ref SDS 19 1550
390726 -
390727 - BI's mission reported on 991222, ref SDS 19 3744, seems to align with
390728 - Tanya's explanation that Doug is demonstrating how large and small
390729 - problems can be addressed by the CODIAK management or problem solving
390730 - process.  This supplements analysis on 000120, ref SDS 20 5110, and
390731 - the letter. ref DIP 1 0001
390732 -
390733 - Tanya advises that CODIAK is an appealing idea. ref DRT 3 5002
390734 -
390735 - CODIAK was reviewed on 991222, and presents an organic cycle for
390736 - addressing different aspects of problems (based on ABC levels of
390737 - complexity) in a comprehensive and orderly manner. ref SDS 19 0786
390738 -
390739 - Mike Taylor presents the Adam Smith explanation of market dynamics
390740 - that allocate resources for solving problems of supply and demand.
390741 - ref DRT 3 2940
390742 -
390743 - Mike goes on to argue that a DKR may not be effective for directing
390744 - social policy in relation to market dynamics. ref DRT 3 8162
390745 - ..
390746 - Tanya seems to suggest that a DKR can enhance capabilities of
390747 - energy buyers to optimizing their procurement practices, and this will
390748 - indirectly cause suppliers to respond constructively. ref DRT 3 3840
390749 -
390750 - An example of what a DKR might add to what is already being done or is
390751 - in train, would be helpful.
390752 -
390753 - Questions on scope of DKR...
390754 -
390755 -     Is the DKR another big data base of stuff like the Internet?
390756 -
390757 -        If so, why do we need another one?
390758 -
390759 -     Is DKR a process, e.g., Doug's ABC and CODIAK, for adding value to
390760 -     inforamtion on the Internet by using the resource productively to
390761 -     solve problems?
390762 -
390763 -        This sounds useful.
390764 -
390765 -        Does it require tools for capturing, organizing, aligning,
390766 -        connecting, analysing, summarizing, uploading and downloading
390767 -        informaion.  Would it be helpful to call all of this for short
390768 -        hand simply "intelligence"?
390769 -
390770 -        What is wrong with current web browsers that currently display
390771 -        information?
390772 -
390773 -     Is DKR a system of controls on who gets what information, and
390774 -     setting policy on human relations that change established "market"
390775 -     dynamics to impose solutions?
390776 -
390777 -        [On 000324 listed these issues for planning DKR project.
390778 -        ref SDS 30 3611
390779 -
390780 -        [On 000407 listed as agenda item for team meetings. ref SDS 33
390781 -        4173
390782 -
390783 -
390784 -
390785 -
390786 -
3908 -

SUBJECTS
Objectives, Collective IQ
Competition Impedes Collaboration Inhibits Sharing
Sharing Information Helps Everyone
Competition, Cooperation, Innate Conflict to Integrated Tools
Tragedy of Commons Competition Inhibits Sharing
Security/Privacy
Privacy, Security - Discovery

4610 -
461001 -  ..
461002 - Competition Limits Value of DKR to Support Collaboration
461003 -
461004 - Tanya Jones quotes Mike Taylor's letter on 000121 citing inherent
461005 - tension between competion and cooperation which must be constructively
461006 - resolved in order for the DKR concept to be effective. ref DRT 3 1848
461007 -
461008 - Mike further comments that we do not know what information is being
461009 - used by market participants whose decisions set prices. But we can be
461010 - quite confident that they are all using the best information they
461011 - have.
461012 -
461013 - This proposition seems like a reach of faith.
461014 -
461015 - People use what seems to satisfy immediate biological requirements
461016 - within their span of attention. People strive at different levels at
461017 - different times in response to perceived needs.  Over time competition
461018 - encourages movement toward better resources, including information,
461019 - but a market can be stable for a long time competing on non-essential
461020 - isues, and thus langor without reliance on the best information,
461021 - because there is satisfaction with the status quo, which is oblivious
461022 - to larger forces at work.  See for example the Pied Piper, discussed
461023 - in connection with reviewing Covey's work on 921205. ref SDS 2 5940
461024 -
461025 - Another, more concrete, example is the worry about new strains of
461026 - infectious diseases that may be forming.
461027 -
461028 - Tanya says the prospect of managing a small fraction of the total
461029 - knowledge base in the world is a tremendous challenge. ref DRT 3 3672
461030 -
461031 - The prospect that anyone would contemplate imposing a knowledge
461032 - managment regimine is worrisome.  On the other hand, Doug and others
461033 - coming forward with ideas on how to manage knowledge at any and all
461034 - levels is a positive step.
461035 -
461036 -
461037 -  ..
461038 - Security Objectives Require Protections for DKR
461039 - Tragedy of Commons Limits Scope of DKR
461040 -
461041 - Mike Taylor describes a "tragedy of the commons" economic problem
461042 - where a shared resource that nobody owns, such as the common grazing
461043 - land in a village or the fish on the Grand Banks, is abused because
461044 - no-one has the economic incentive to manage and care for it. The DKR
461045 - would have such a problem - it appears to depend on altruism for its
461046 - content rather than economic advantage. ref DRT 3 1140
461047 -
461048 - Tanya disagrees that this a "tragedy of the commons" problem. The DKR
461049 - could provide several valuable services: as a publication system, it
461050 - can provide the means to protect intellectual property; as a
461051 - searchable database, it will enable a means of getting answers to
461052 - questions. How well it does these things depends on the quality of
461053 - system development. ref DRT 3 1435
461054 - ..
461055 - Tanya would like to see the DKR allow for a company or
461056 - individual to store both *public and private* information with
461057 - appropriate degrees of security. It is much easier to learn a single
461058 - (if evolving) tool system. ref DRT 3 2016
461059 -
461060 - Privacy and security for Knowledge Space were reviewed on 981107.
461061 - ref SDS 5 4494
461062 -
461063 -     [On 000129 Colloquium class 4 discussed privacy. ref SDS 23 0897]
461064 -
461065 - One self-interest dynamic that reduces the problem of deleting
461066 - unimportant information, which Mike forsees, is that when people
461067 - create information, as in this record, it is generally aimed at
461068 - advancing an interest, most often economic, but it could be to plan a
461069 - birthday party, or something like that.  Creating information, as in
461070 - this record takes time, which is precious.  Any such investment, must
461071 - therefore be valuable in some context.
461072 -
461073 - The people who generate information are managing it toward achieving
461074 - objectives.  Others who share the same objectives may be involved in
461075 - contributing or collaboring to leverage the value of information.  So,
461076 - the idea that there is a lot of unneeded information is not supported
461077 - by the record, where the human mind uses all of its knowledge to set
461078 - meaning of new information, reported on 960321 explaining "induction,"
461079 - ref SDS 3 2882, although the majority of this adjustment occurs in the
461080 - subconscious.  It is therefore risky to delete information, because
461081 - the impact is unpredictable.
461082 -
461083 - Limited time and span of attention present a larger risk of failure
461084 - than security.
461085 -
461086 - Everyone is busy trying to communicate and discover correlations and
461087 - implications from information in constant meetings, calls, and
461088 - documents to improve earnings.  The time required to accomplish this
461089 - task reduces the time available for prying into "private" information.
461090 - People looking at your "private" information, overlook intelligence in
461091 - their own Knowledge Space under the rule that management is a process
461092 - of continual bumbling.  Therefore, the liklihood of doing something
461093 - useful with unathorized information, in an environment of information
461094 - overload is very low.  Most likely it will be mishandled, misdirected
461095 - and forgotten, because people do have enough time to think, as
461096 - reported on 970910. ref SDS 4 3479
461097 -
461098 - In any case, some security measures are already available, as Tanya
461099 - points out.
461100 -
461101 -
461102 -
461103 -
461104 -
461105 -
461106 -
461107 -
461108 -
461109 -
461110 -
461111 -
461112 -
461113 -
461114 -
461115 -
461116 -