CONTACTS 

SUBJECTS
Email XML Seed Team Use What is Available, 000302
Email Hackable WebLog Organizing and Thought Tracking, 000428
Knowledge Difficult to Understand Difference from Information
Armstrong, Eric Knowledge Difficult to Understand Difference from Inf
Knowledge Difficult to Understand Difference from Information
Information Knowledge Mean Same Thing Difference Hard for People to U
Knowledge Management Give Up Frustrated Disillusioned Clueless Softw

4609 -
4609 -    ..
4610 - Summary/Objective
4611 -
461101 - Follow up ref SDS 29 0000, ref SDS 28 0000.
461102 -
461103 - Received ref DRT 1 0001 from Jack Park citing a recent letter from
461104 - Eric Armstrong, which is not in the record.
461106 -  ..
461107 - Jack initially quotes Eric...
461108 -
461110 -      ..
461111 -     Email Enhancement is Doeable for DKR Project Team
461112 -     Project Must Focus What Can be Done - Email
461113 -
461114 -     So I am focused on what we can build today that will help us carry
461115 -     on those conversations. ref DRT 1 5712
461116 -
461117 -     In a second letter Eric confirms he has been advocating an email
461118 -     interface, and a distributed data model, similar to email.
461119 -     ref DRT 3 2714
461120 -
461121 -         [...below, Eric explains email offers a path for what the team
461122 -         is trying to accomplish to improve communication to share
461123 -         information, collaborate, and organize the record efficiently
461124 -         for Knowledge Management to find things that make people more
461125 -         productive. ref SDS 0 F82E
461127 -          ..
461128 -         [On 000503 sent proposal to Jack and Eric. ref SDS 30 0252
461130 -          ..
461131 -         [On 000505 Eric submits requirements for a Collaborative
461132 -         Document System (CDS) as core capability the project will
461133 -         initially develop. ref SDS 34 4392
461135 -          ..
461136 -         [On 010321 POIMS explains two branches of KM. ref SDS 53 0001
461138 -      ..
461139 -     Joe Williams sends a letter noting the urgency of improving email
461140 -     based on past 30 email flying every which way, that makes it
461141 -     difficult to assemble a coherent thought or direction for the
461142 -     project. ref DRT 4 0001
461143 -
461145 -          ..
461146 -         Connections that Maintain Alignment Make Information Useful
461147 -
461148 -         I mean one thing the DKR/OHS must give us is a simpler way for
461149 -         one or a group to take all those last 30+ messages, glean the
461150 -         important parts, organize and consolidate these important
461151 -         parts, then republish the refinement to those who wish to
461152 -         study the topic outside the relative chaos of an e-mail type
461153 -         system.  The new item includes references to all the previous
461154 -         items so that someone could go back to verify proper
461155 -         extraction, but most importantly, maintain the link with
461156 -         underlying facts or assumptions in case they change, requiring
461157 -         a change to the new node, This is how we can evolve knowledge
461158 -         about a particular topic. ref DRT 4 B45L
461159 -
461160 -            [On 000505 Eric proposes email to accomplish Knowledge
461161 -            Management, which seems conflicting with experience showing
461162 -            email is inefficent and disorganized, as Joe relates today.
461163 -            ref SDS 34 OF69
461165 -             ..
461166 -            [On 011003 Eric says email creates information overload
461167 -            that paralyzes productivity, requests clues for solution.
461168 -            ref SDS 58 EC5N
461170 -             ..
461171 -            [On 040113 Tom Munnecke submits ideas on improving
461172 -            productivity of management and communication by
461173 -            better organization of email. ref SDS 63 XP7J
461175 -          ..
461176 -         This is a good explanation of POIMS, ref OF 1 0561, which is
461177 -         pretty much what is shown in SDS records that Joe and the DKR
461178 -         team have encountered, yet only Jack has come forward to state
461179 -         that point, per below. ref SDS 0 6138
461180 -
461182 -      ..
461183 -     Project Team Miscommunicating on KM for Weeks
461184 -     Knowledge Markety Buzzword, Needs Definition to Guide the Work
461185 -
461186 -     Eric advises that to achieve a better "separation of concerns", I
461187 -     am going to try to avoid use of the term "knowledge" in this
461188 -     forum.  I use it only as a markety buzzword, to distinguish this
461189 -     effort from data base systems and the like. But it tends to flood
461190 -     me with issues I'm not prepared to deal with at the moment.
461191 -     ref DRT 1 3053
461193 -  ..
461194 - Eric's problem understanding "knowledge" today seems conflicting with
461195 - his letter on 000423 describing the purpose of Knowledge Management
461196 - with an OHS/DKR is to create and organize documentation of daily work,
461197 - ref SDS 21 5933, that provides a computer resource which "augments
461198 - human intelligence". ref SDS 21 5096
461200 -  ..
461201 - Difficulty understanding difference between information and knowledge
461202 - was cited on 940722. ref SDS 1 8388
461204 -  ..
461205 - On 980226 IBM describes Knowledge Management with marketing
461206 - terminology of "business intelligence" to replace technology for
461207 - "information management." ref SDS 8 2716
461209 -  ..
461210 - Aligns with consideration on 000406 to meet on defining KM for use
461211 - case analysis. ref SDS 14 3722
461213 -         ..
461214 -        On 000407 action item set for the team to develop foundational
461215 -        understanding of "knowledge." ref SDS 15 2805
461217 -  ..
461218 - On 000425 KM is a secret of SDS. ref SDS 23 0480  On 950710 Landauer
461219 - reported software engineers don't understand how to program computers
461220 - to help people think. ref SDS 2 3375
461221 -
461222 -           [On 000504 Eugene submits explanation that distinguishes
461223 -           information from knowledge. ref SDS 32 0007
461225 -            ..
461226 -           [On 000504 Doug Engelbart reports more understanding of
461227 -           knowledge needed for NSF support. ref SDS 33 4C4F
461229 -            ..
461230 -           [On 000517 Eric met at Intel with Intel to define knowledge
461231 -           and develop common vision of knowledge management.
461232 -           ref SDS 38 5096  He confirmed not having a good grasp of
461233 -           these issues. ref SDS 38 5092
461235 -            ..
461236 -           [On 000518 "knowledge" defined at project meeting.
461237 -           ref SDS 39 5555
461239 -            ..
461240 -           [On 000531 architecture human thought predicate to
461241 -           architecture for KM that augments human intelligence.
461242 -           ref SDS 40 4256
461244 -            ..
461245 -           [On 000615 OHS/DKR team discouraged nobody knows what we are
461246 -           trying to accomplish, lack of progress causes engineers to
461247 -           give up on Knowledge Management; decide to improve email and
461248 -           call it OHS/DKR. ref SDS 43 6271
461250 -            ..
461251 -           [On 000723 Cliff Joslyn with LANL commented that KM is
461252 -           becoming out dated. ref SDS 45 1804
461254 -            ..
461255 -           [On 000824 Eric is not comfortable using organizational
461256 -           memory (archives), ref SDS 46 7O9I, which avoids study of
461257 -           cognitive science. ref SDS 46 G37G
461259 -            ..
461260 -           [On 001017 DKR team reports funding to produce OHS, and that
461261 -           vision for architecture is pending. ref SDS 48 4877
461263 -            ..
461264 -           [On 001018 Eric reports architecture snags. ref SDS 49 GD6J
461266 -            ..
461267 -           [On 001127 Eric reports many people have general ideas about
461268 -           improving information technology, but creating support for
461269 -           knowledge is hard to understand. ref SDS 51 QI4O
461271 -            ..
461272 -           [On 001130 IBM spend $4B and had to abandon effort on
461273 -           converting Lotus Notes to support Knowledge Management,
461274 -           because engineers could not agree on what knowledge means.
461275 -           ref SDS 52 F26K
461277 -            ..
461278 -           [On 010916 Eric discouraged can't find anything using IT
461279 -           methods everybody likes. ref SDS 57 KA6H
461281 -            ..
461282 -           [On 011003 Eric more discouraged that productivity paralyzed
461283 -           because nobody can find anything using popular programs.
461284 -           ref SDS 58 EC5N
461286 -            ..
461287 -           [On 020608 knowledge define case study hard for people to
461288 -           grasp, ref SDS 60 CC6J; philosophy practice grounding for
461289 -           "Knowledge Management" reviewed 050115, ref SDS 65 SF5K,
461290 -           correlates with cognitive science reviewed 960518,
461291 -           ref SDS 5 GS58, management tasks considered 000307,
461292 -           ref SDS 12 767G, and physical science locality principle
461293 -           power of knowledge predicts and controls the future,
461294 -           reviewed on 040312, ref SDS 64 YH4G
461296 -            ..
461297 -           [On 020718 Eric submits definition of knowledge. ref SDS 61
461298 -           YX9L
461300 -         ..
461301 -        On 000419 Doug Engelbart called for DKR team to define
461302 -        knowledge. ref SDS 16 4964
461304 -         ..
461305 -        On 000428 made similar point that project discussion shows lack
461306 -        of understanding about "knowledge." ref SDS 27 1155
461308 -      ..
461309 -     I know that an AI-style "knowledge" repository is outside my
461310 -     present scope. ref DRT 1 2142
461311 -
461313 -  ..
461314 - Eric notes in a second letter that...
461315 -
461316 -     We have been fundamentally miscommunicating about what we mean by
461317 -     a "knowledge repository" for weeks, now. ref DRT 3 4118
461318 -
461319 -           [In another record today, Eric notes disagreement about
461320 -           Knowledge Repository. ref SDS 30 5933
461322 -            ..
461323 -           [On 000602 report that DKR is difficult to define.
461324 -           ref SDS 42 6162
461326 -            ..
461327 -           [On 001116 Eric continues to defer work on defining a "DKR."
461328 -           ref SDS 50 SV8I
461330 -          ..
461331 -         Aligns with the letter to Morris on 000425 that design for
461332 -         Knowledge Management is a secret of SDS. ref SDS 23 0480 Also,
461333 -         aligns with letter to Jack on 000428 citing the disconnect
461334 -         between work being done and objective to produce a Knowledge
461335 -         Management capability. ref SDS 27 0001
461337 -          ..
461338 -         When people recognize miscommunication, that is the first
461339 -         opportunity for real communication to begin.
461341 -  ..
461342 - Eric continues...
461343 -
461344 -     I'm looking forward to seeing a knowledge repository one day. But
461345 -     we need to be very clear about the scope of the current project,
461346 -     and what we mean by "knowledge repository", so we can be clear
461347 -     about what we are building. ref DRT 3 4960
461349 -  ..
461350 - This goes to definitions of "knowledge" and for "respository" per the
461351 - record on 971021 setting objective to create this capabilty by porting
461352 - SDS record to the Internet. ref SDS 7 3636
461354 -  ..
461355 - On 000208 Eric reported uncertainty about what to build for a
461356 - knoweldge repository. ref SDS 10 027P  He asked how to integrate email
461357 - and hyperdocuments. ref SDS 10 3596  He asked what the core of
461358 - Knowledge Management system should do? ref SDS 10 4320
461360 -  ..
461361 - At that time, a letter responded on 000208 citing POIMS requirements
461362 - for "intelligence" support in a flexible structure of Knowledge Space.
461363 - ref SDS 10 DH47
461365 -  ..
461366 - A few days later on 000212 Eric's letter proposed in part...
461367 -
461368 -              Capturing design notes for each part of the OHS/DKR
461369 -              specification, as they arise in the mind from meetings,
461370 -              calls, documents and performing daily work.  This record
461371 -              on "design notes" would not appear in the "functional
461372 -              specification." But work to prepare the design document
461373 -              could draw on the resource by a request that says...
461374 -
461375 -                  "Give me all the design notes that correspond to this
461376 -                  version of the specification". ref SDS 11 YA4F
461378 -               ..
461379 -              Eric recalls thinking a "document" shouldn't be an
461380 -              isolated entity, but rather a "labeled view" on a nexus
461381 -              of nodes.  He feels now that a means is needed for
461382 -              starting new documents by using thinking from prior
461383 -              related endeavors, commonly called "experience."
461384 -              ref SDS 11 1682
461386 -  ..
461387 - Review at that time on 000212 indicated Eric's proposal would be a big
461388 - step toward a model of Knowledge Space. ref SDS 11 G454
461390 -  ..
461391 - How did such insightful analysis devolve to email?
461393 -            ..
461394 -           [On 000928 Eugene Kim reports project deliverables are not
461395 -           well understood. ref SDS 47 X57F
461397 -            ..
461398 -           [On 001116 Eric continues to defer work on defining a "DKR."
461399 -           ref SDS 50 SV8I
461400 -
461402 -      ..
461403 -     Email Not Proper Target for Effective DKR Capability
461404 -     Reaching for Difficult, Novel Solution in AI-Style DKR
461405 -
461406 -     On 000420 the project team noticed conventional email is fast and
461407 -     easy, and so considered making enhancements to email the core
461408 -     capability of the DKR project. ref SDS 17 0784   On 000423 Eric
461409 -     explained this objective, after saying the purpose of the DKR is
461410 -     to augment human intelligence. ref SDS 21 5943
461412 -           ..
461413 -          [On 000505 Eric submits requirements for a Collaborative
461414 -          Document System (CDS) as core capability the project will
461415 -          initially develop. ref SDS 34 4392
461416 -
461417 -
4615 -

SUBJECTS
OHS/DKR Knowledge Management Define Purpose SDS Knowledge Space Link

6703 -
670401 -  ..
670402 - Knowledge Space Email Links Addressability Component OHS/DKR
670403 -
670404 -
670405 - Jack responds to Eric...
670406 -
670407 -     But, an AI-style "knowledge" repository is not outside Jack's
670408 -     scope.  It is the sole reason I am involved. I am far less
670409 -     interested in doing the doable. There's already tons of stuff out
670410 -     on the web doing that. I'm vastly more interested in doing the
670411 -     hard, so hard, in fact, that Doug has only scratched the surface
670412 -     of it.  Eudora would do just fine if email is all we need.  A
670413 -     relational database with a good sql interface would do fine if all
670414 -     we want is to warehouse factoids. I don't know about you, Eric,
670415 -     but I want more. Lots more.  What I want is hard, nothing less.
670416 -     And, settling for what's doable is just liable to make it
670417 -     impossible to append what's hard on as an afterthought.
670418 -     ref DRT 1 2870
670420 -  ..
670421 - Jack comments on "Knowledge Space" - a Breakthrough??
670422 -
670423 -     I want the ability to roam around in knowledge space, looking for
670424 -     interesting ideas, things others didn't think of.  Can't do it
670425 -     with an email system.  Sorry. ref DRT 1 0154
670426 -
670427 -         Jack argues for advancing beyond information technology,
670428 -         rather than giving up, because "knowledge" is a difficult
670429 -         concept for Eric to understand, per above. ref SDS 0 5033
670431 -          ..
670432 -         The reference to Knowledge Space reflects Jack's report to the
670433 -         team on 000426 commending SDS and POIMS, as proof of concept.
670434 -         ref SDS 24 3315
670435 -
670436 -            [On 000504 Jack commends POIMS, SDS "things we don't talke
670437 -            about around here." ref SDS 32 6082
670439 -             ..
670440 -            [On 000505 Eric responds to Jack's argument by including
670441 -            strong analysis in v0.5 of project specs for an OHS that is
670442 -            centered on an email model. ref SDS 34 4392
670444 -             ..
670445 -            [On 000518 Mary Keeler presents ideas on knowledge from
670446 -            philosophy research that supports Jack's objective for
670447 -            knowledge space. ref SDS 39 8439
670449 -             ..
670450 -            [On 000711 Jack is back to "documents" as the lowest level
670451 -            of information in a DKR architecture. ref SDS 44 1508
670453 -             ..
670454 -            [On 010908 Jack feels laziness makes email attractive for
670455 -            improving productivity. ref SDS 54 0001
670457 -             ..
670458 -            [On 030314 Jack seems to give up on separating knowledge
670459 -            from information, argues knowledge management only occurs
670460 -            in the mind, and argues SDS support for "intelligence"
670461 -            processes are "information management." ref SDS 62 5531
670463 -          ..
670464 -         Yay, to both guys!  Eric is correct that we have to work on
670465 -         what is produceable, and Jack is right that we can provide
670466 -         effective KM, one derivitive of which will be more productive
670467 -         email.
670469 -          ..
670470 -         On 000212 Eric proposed an "innovation" that recognized the
670471 -         potential to move beyond the constraints of "documents" as the
670472 -         primary medium of information, and develop an effective
670473 -         "Knowledge Space." ref SDS 11 9790
670475 -          ..
670476 -         Both are also wrong.
670478 -          ..
670479 -         If Eric does not understand "knowledge" then call the team to
670480 -         arms.  Invest some of his tremendous work capacity to follow
670481 -         the leader's request on 000307 to do a work up like Bellinger,
670482 -         ref SDS 12 4820, and again on 000419 to define "knowledge."
670483 -         ref SDS 16 4964
670485 -          ..
670486 -         Jack is wrong to just say don't do email because it is easy.
670488 -          ..
670489 -         Come forward with a definition of knowledge that helps Eric
670490 -         and the guys focus on things that need to be built.  Try
670491 -         strarting with definitions of "intelligence" and "knowledge"
670492 -         in POIMS. ref OF 1 0561  Look at Bellinger's work on 000307,
670493 -         as suggested by Doug. ref SDS 12 4012  Don't just say read
670494 -         Rod's white papers and look at the web site.  Dig in and
670495 -         respond with specific quotes that provide a working definition
670496 -         which permit someone to go build things that implement the
670497 -         definition.
670499 -          ..
670500 -         To be clear, it is not an easy job; but Jack has a lot of
670501 -         help.
670503 -          ..
670504 -         Andy Grove says that helping people grasp new ideas and a new
670505 -         direction, to help people who just don't get it, is not easy
670506 -         and is not fun, reported on 980307. ref SDS 9 3761, and
670507 -         ref SDS 9 2648  It is like walking through the valley of
670508 -         death. ref SDS 9 4674  But Jack says he is looking for the
670509 -         hard job, so this is it, as evidenced by Eric's willingness to
670510 -         say, "Hey, I don't get it, help me out!"
670512 -          ..
670513 -         Jack makes a good start by observing he wants the power to
670514 -         roam around in Knowledge Space.  That is a powerful idea.
670515 -         Define Knowledge Space from POIMS, ref OF 1 1107, and the
670516 -         record on 960620. ref SDS 6 3516
670518 -          ..
670519 -         Let's get going.  Use the help at hand -- call Rod.
670520 -
670521 -           [In another record today, Eric notes disagreement about
670522 -           Knowledge Repository. ref SDS 30 5933
670523 -
670524 -           [On 000504 talked to Eric about proposal. ref SDS 31 1320
670526 -            ..
670527 -           [On 000515 Professor Mary Keeler's research paper on Charles
670528 -           Peirce's work supports definition of "knowledge" as grounded
670529 -           in experience. ref SDS 36 0042
670531 -            ..
670532 -           [On 000516 Jack submitted definition of "knowledge" from a
670533 -           professional source. ref SDS 37 4723
670535 -            ..
670536 -           [On 000517 met with Eric and Morris at Intel to develop
670537 -           common vision Knowledge Management, defined "knowledge."
670538 -           ref SDS 38 0785
670540 -            ..
670541 -           [On 000518 Professor Keeler gave presentation to team at SRI
670542 -           on "knowledge," providing sufficient informational resources
670543 -           to develop working definition of "knowledge." ref SDS 39
670544 -           8439
670546 -            ..
670547 -           [On 000601 Bill Bearden submitted initial glossary for the
670548 -           project. ref SDS 41 0001
670549 -
670550 -
670551 -
670552 -
670553 -
670554 -
6706 -

SUBJECTS
Email OHS/DKR Use Cases Communicate Collaborate Organize Find Inform

8303 -
830401 -  ..
830402 - Email Disorganization Disorder Fails Records Management Communication
830403 - Illusion Progress Email Brings Contiual Error Without Alignment
830404 - Slashdot Less Efficient than Email Organize Record Subject Threads
830405 - Email Fast Easy Cheap Communication Collaboration Illusion Productivity
830406 -
830407 - Follow up ref SDS 29 0001, ref SDS 28 5933.
830408 -
830409 - Received ref DRT 2 0001 from Eric responding to a letter from Jon
830410 - Winters which says...
830411 -
830412 -      As much as I love Slashdot I must admit that I check it once or
830413 -      twice a day and rarely reply to the stories.  I'll submit news
830414 -      about once a month.  OTOH I have spent a great deal of time
830415 -      reading almost every email on this list and I contribute almost
830416 -      every day. (often more than once per day), ref DRT 2 0001
830418 -  ..
830419 - This report indicates that the SlashDot work process is not
830420 - sufficiently malable to fit into daily work patterns.  Jon's steady
830421 - contribution to Doug's DKR project using regular email seems to
830422 - support Eugene Kim's point yesterday, ref SDS 29 0001, and aligns with
830423 - project team review of email on 000420 as a fast and easy way to
830424 - manage daily working information. ref SDS 17 0784
830425 -
830426 -
830428 -  ..
830429 - Communicate Collaborate Teamwork Share Organize Find Information
830430 - Use Cases Knowledge Management Email Share Information Communicate
830431 - Email Seems Help What People Are Trying to Accomplish Good Management
830432 -
830434 -  ..
830435 - Eric lists common use cases for Knowledge Management, implementing
830436 - procedures proposed during the program launch meeting at SRI on
830437 - 000324. ref SDS 13 6052  Today Eric explains why email seems fast and
830438 - easy that presents an illusion of progress...
830439 -
830440 -    1.  It is central to my daily activities, because....
830442 -  ..
830443 - How are daily activities linked to align with priorities, objectives
830444 - and requirements of the work, and commitments for getting things done,
830445 - rather than being pushed around by email from others?  Management
830446 - standards call for traceability to original sources, reviewed on
830447 - 950721. ref SDS 3 1740
830449 -             ..
830450 -            [On 000505 Eric submits requirements for a Collaborative
830451 -            Document System (CDS) with email as core capability.
830452 -            ref SDS 34 4392
830454 -             ..
830455 -            [On 000824 Eric relates SRI team started OHS/DKR project
830456 -            listing use cases, but efforts fragmented and failed to be
830457 -            productive. ref SDS 46 MVE8
830459 -  ..
830460 - POIMS lists email advantages and limitations supporting Knowledge
830461 - Management. ref OF 1 CZ6K
830462 -
830463 -            [On 010321 background on email problems leading to
830464 -            explanation in POIMS ref SDS 53 ID6M
830466 -  ..
830467 - Eric continues...
830468 -
830469 -    2.  Information comes to me instead of having to go searching
830470 -        for it, and because the....
830472 -  ..
830473 - Eric's proposal to improve email fits Joe Williams' report today that
830474 - email on the OHS/DKR project is disorganized and overwhelming, and so
830475 - prevents progress, per above. ref SDS 0 C48F  Eric's explanation that
830476 - email avoids searching for information, and below, that email makes an
830477 - action item list, and organizes things efficiently, ref SDS 0 TT68,
830478 - seems conflicting, oblivious, and willfully blind to reality of
830479 - experience Joe presents today. ref SDS 0 5456
830480 -
830481 -           [On 000505 Eric proposes email for OHS/DKR system because
830482 -           information comes to you like "one stop shopping" for
830483 -           [everything] that needs attention. ref SDS 34 3000
830485 -            ..
830486 -           [On 000615 OHS/DKR team discouraged nobody knows what we are
830487 -           trying to accomplish, lack of progress causes engineers to
830488 -           give up on Knowledge Management; decide to improve email and
830489 -           call it OHS/DKR. ref SDS 43 6271
830491 -             ..
830492 -            [On 011003 Eric says email creates information overload
830493 -            that paralyzes productivity, requests clues for solution.
830494 -            ref SDS 58 EC5N
830496 -             ..
830497 -            [On 020530 case study what are we trying to accomplish
830498 -            asked repeatedly until people give up trying to develop
830499 -            technology for Knowledge Management. ref SDS 59 EF7I
830501 -  ..
830502 - Reactive management relying on last-in-first-out (LIFO) practices
830503 - creates piles up mountains of information on computers without
830504 - organization.  Lack of order prevents finding critical details neither
830505 - can people assemble chronologies within contextual frames that reveal
830506 - cause and effect to make sense of complex events.  Eric's comment that
830507 - email avoids having to search for information conflicts with reality.
830508 - Example on 960406 shows people pay a big price constantly searching
830509 - for information. ref SDS 4 5922  At that time, Morris noted this
830510 - remains a big problem. ref SDS 4 4249
830511 -
830512 -            [On 010911 the United States paid a big price when
830513 -            terrorists struck in New York and Washington DC because
830514 -            finding inforamtion takes too much time. ref SDS 55 YNGH
830516 -  ..
830517 - Good management requires proactive effort, i.e., front-end investment,
830518 - expending time and energy to add intelligence "connecting the dots" of
830519 - cause and effect.  Connecting information in email and other sources
830520 - into the power of knowledge enables command and control of the record
830521 - that makes leadership effective, explained in POIMS. ref OF 1 1113
830523 -             ..
830524 -            [On 040312 "locality" principle relates energy exchange
830525 -            between cause and effect yields the power of knowledge for
830526 -            predictability that controls the future. ref SDS 64 YH4G
830528 -  ..
830529 - Eric continues...
830530 -
830531 -    3.  Threading helps me organize things effectively. ref DRT 2 J46H
830533 -  ..
830534 - Threading basically means a letter has a subject string.
830536 -  ..
830537 - Email subject "threads" may organize things on another planet.  Email
830538 - "subject" threads almost immediately become irrelevant, disconnected
830539 - from the content causing disorder, and disorganization that paralyzes
830540 - productivity because nobody can find inforamtion piling up on
830541 - computers.
830542 -
830543 -            [On 010908 Jack Park reports laziness drives people to hit
830544 -            the reply button and impulsively type what ever pops into
830545 -            the mind without consideration of subject, ref SDS 54 YF3I,
830546 -            resulting in email not being well organized. ref SDS 54
830547 -            US8O
830549 -             ..
830550 -            [On 010916 Eric cites email supported by SDS that applies
830551 -            applies amazing memory based on methods to organize
830552 -            information that obviously work. ref SDS 56 0001
830554 -             ..
830555 -            [On 011003 Eric complains email paralyzes productivity
830556 -            because information density overwhelms span of attention;
830557 -            email cannot be organized so nobody can find anything in
830558 -            time to be effective. ref SDS 58 EC5N
830560 -  ..
830561 - Eric has the right instincts, that information needs to be organized
830562 - in order to help people use it, but this is the role of Jack's
830563 - ontology or the organic structure of context using subject indexing,
830564 - explained in POIMS. ref OF 1 1110
830566 -  ..
830567 - Eric continues...
830568 -
830569 -    4.  What it is missing in email is Slashdot functionality (wrt
830570 -        evaluations and the capacity to ignore threads), editability,
830571 -        and Traction functionality (wrt categories). ref DRT 2 6624
830573 -         ..
830574 -    5.  Both SlashDot and Traction are missing a good sense of
830575 -        hierarchy and view control.  Which is where we stand to make a
830576 -        serious contribution. ref DRT 2 1920
830578 -         ..
830579 -    6.  But as Lee points out, a Zope/Squishdot system presents a lot
830580 -        of room for hacking. *Especially* if we use some sort of
830581 -        Gnutella-enabled "eMail" app, so that additions and changes we
830582 -        make are broadcast either directly to others, or perhaps sent
830583 -        to the server, where they are rebroadcast (possibly after
830584 -        transcoding to replace user-specific node IDs with global
830585 -        system IDs). ref DRT 2 4293
830587 -  ..
830588 - Eric lists various technologies to use for Knowledge Management hoping
830589 - to avoid reinventing the wheel, proposed at SRI during the project
830590 - launch meeting on 000324. ref SDS 13 JY4F
830592 -  ..
830593 - Eric continues...
830594 -
830595 -    7.  So we might be able to make such a system behave like email.
830596 -        Even if it takes a separate "email" app for now, it would still
830597 -        have the proper behaviors. ref DRT 2 7272
830599 -         ..
830600 -    8.  And Squishdot, being Squeak/Smalltalk based, strikes me as
830601 -        potentially *very* hackable... ref DRT 2 9296
830602 -
830603 -
830604 -
830605 -
830606 -
830607 -
830608 -
830609 -
830610 -
830611 -
830612 -
830613 -
8307 -