CONTACTS 

SUBJECTS
OHS/DKR Meeting at SRI 000622
DKR Architecture, Jack Park, 000623
DKR Needs Architecture, 000426, Jack Park
Ontology Organization Method
Knowledge, Intelligence, Define 000307
Magister Ludi Controls Glass Bead Game
Links Added to Original Documents Proposed SRI Team on 000622
Links Formed Above Original Docs, Jack Park, 000623
Collaboration Too Limited for Objective DKR, Must Expand to Knowledge
Addressability Anchors Original Docs for Linking
Collaboration, Ontology, Core Capability DKR, Jack, 000623
Ontology Engine Epistomology, Jack Park
Changing Original Work of Others Incorrect OHS Design

3615 -
3615 -    ..
3616 - Summary/Objective
3617 -
361701 - Follow up ref SDS 46 0000, ref SDS 43 0000.
361702 -
361703 - Jack reports progress during the meeting at SRI yesterday. ref SDS 0
361704 - 7492  He proposes an architecture for a DKR initially grounded in
361705 - subject management, which he is calling ontology. ref SDS 0 9900 A
361706 - 3-layer system is proposed that entails capturing information,
361707 - developing a consensus subject index (epistomology), developing a
361708 - software program that processes the record to assign subjects, and a
361709 - searching program to assemble the record using the ontology (subject
361710 - index, epistomology). ref SDS 0 5475  There is discussion that this
361711 - will aid collaboration, and/or that the ontology is formulated through
361712 - collaboration. ref SDS 0 4752  Jack provides an initial explanation of
361713 - how the system is used, ref SDS 0 5840, that supports a Communication
361714 - Manager role; however, Jack expects software can be designed to do
361715 - this "management" function. ref SDS 0 0784  In the spirit of advancing
361716 - the architecture several questions arise. ref SDS 0 4048
361717 -
361718 -      [On 000624 sent letter to Mary Keeler on KM. ref SDS 49 1534
361720 -       ..
361721 -      [On 000627 called Jack to follow up. ref SDS 50 0001
361723 -       ..
361724 -      [On 000629 sent letter on architecture. ref SDS 51 0001
361726 -       ..
361727 -      [On 000710 Jack formalizes architecture in a conceptual graph.
361728 -      ref SDS 52 0001
361729 -
361730 -
361732 -  ..
3618 -
3619 -
3620 - Progress
3621 -
362101 - Categories are Rigid Using Ontology Methods, Need Dynamic Methods
362102 - Team Defining Knowledge, Category, Document, Node with Use Cases
362103 -
362104 - Received ref DRT 1 0001 from Jack discussing progress during the
362105 - meeting yesterday at SRI, and offering ideas to advance the work on
362106 - developing a DKR architecture.
362107 -
362108 - At that meeting, OHS was defined as Doug's Augment + Categories.
362109 - ref SDS 47 6652
362111 -  ..
362112 - Jack initially concurs, ref DRT 1 9270, with a letter from Gil Regev
362113 - about "categories" becoming rigid. ref DRT 1 9555
362114 -
362115 -     On 000505 Eric Armstrong submitted CDS (OHS) specs v0.5 that has a
362116 -     section for "Categories" and discusses "nodes," similar to what
362117 -     Jack has been calling "Ontology." The record calls for review of
362118 -     critical issues, ref SDS 25 5003  On 000601 Eric submitted specs
362119 -     v0.7 expanding work on "Categories" which needs further work to
362120 -     address empathic design issues of usefulness. ref SDS 36 5933
362122 -      ..
362123 -     Human cognition creates subjects along an organic continuum, which
362124 -     are fluid and dynamic at the molecular level, comprising a dilemma
362125 -     of knowledge management to establish useful structure. per POIMS.
362126 -     ref OF 1 0561
362128 -      ..
362129 -     SDS helps people create and maintain an organic subject structure
362130 -     that reflects more closely what is actually occurring in the mind.
362131 -     This is a flexible environment, and so may avoid the concern Gil
362132 -     raises today about "rigid" categories.
362134 -      ..
362135 -     People tend to force everything into a rigid framework of existing
362136 -     subjects because they do not have awareness, tools nor procedures
362137 -     for managing organic subject structure.
362139 -  ..
362140 - Jack was disappointed by slow progress on architecture for a DKR, as
362141 - the team struggles with definitions for "document" and "node."
362142 - ref DRT 1 5934  He and I discussed this prior to the meeting yesterday
362143 - based on disclosure at the meeting last week that the project team
362144 - cited "lessons learned" to defer work on a DKR because there is not
362145 - enough known about knowledge and knowledge management. ref SDS 45 6271
362146 -
362147 -     [On 000815 meetings at SRI cancelled pending development of
362148 -     architecture. ref SDS 56 0001
362150 -  ..
362151 - Yesterday, I responded to Eugene's letter relating progress with OHS
362152 - by adding categories to Augment, and indicated meaning of "node" is
362153 - not clear i the record. ref SDS 48 5022
362155 -  ..
362156 - Jack reports today that Eugene did a good job summarizing use cases.
362157 - ref DRT 1 2989
362159 -      ..
362160 -     On 000615 Eugene proposes relying on an intuitive sense about
362161 -     knowledge to develop use cases, rather than the project record,
362162 -     and recognized authority. ref SDS 45 0051
362164 -      ..
362165 -     Jack does not report on efforts to rely on the project glossary
362166 -     definition, the project record, or any other authority to guide
362167 -     development of use cases for KM, as noted in the record on 000615.
362168 -
362169 -
362171 -  ..
362172 - Ontology Core of Architecture for DKR
362173 - Architecture Provides Framework for DKR Based on Consensus Ontology
362174 - Progress on DKR with Initial Ideas on Architecture
362175 -
362176 - Jack recognizes frustration about slow progress on understanding the
362177 - scope of OHS/DKR because people are afraid to grapple with the meaning
362178 - of knowledge, reported on 000615, ref SDS 45 6271, based on Eric
362179 - Armstrong's report on 000503, ref SDS 24 5033, asking......
362181 -                     ..
362182 -                    What's a mother to do?
362183 -
362184 - ....to encourage review of requirements and procedures for organizing
362185 - the record, which he describes as "ontology."
362187 -  ..
362188 - Jack proposes a consensus ontology to guide and expedite the work of
362189 - the project. ref DRT 1 5742   This aligns with Eric Armstrong's ideas
362190 - about catagories, subjects and topics on 000601. ref SDS 36 5933
362192 -  ..
362193 - Jack and Eric do not provide examples illustrating how an ontology of
362194 - OHS/DKR would be developed, what it looks like, how long it takes to
362195 - create, and once created, how much effort is required to maintain it,
362196 - who has the skills for this work, and what value an ontology would add
362197 - to current work practice using email.  Nothing is submitted on cost
362198 - and benefits, nor is there a template to follow for doing the work.
362200 -      ..
362201 -     The need to organize the work is part of "intelligence" set out in
362202 -     POIMS. ref OF 1 0561
362203 -
362204 -        [On 000718 SRI pre-proposal to NASA does not offer technical
362205 -        capability for catagories nor ontology. ref SDS 54 2166
362206 -
362207 -        [On 011003 Eric Armstrong frustrated information overload
362208 -        paralizes productivity; analysis hopeless quagmire; wants
362209 -        system to categorize. ref SDS 76 SW9L
362211 -      ..
362212 -     The complexity and fluidity of subjects make it impossible to form
362213 -     a complete consensus, because subjects are constantly growing in
362214 -     all directions, and at different rates for each person every day,
362215 -     per analysis on....
362216 -
362217 -          890523 scope of subject management....... ref SDS 1 P13O
362218 -          910221 DNA organic structures............ ref SDS 2 OP7M
362219 -          970116 dilemma subjects complex useful... ref SDS 8 9539
362221 -      ..
362222 -     Jack cited this dilemma in his letter to the Colloquium on 000221.
362223 -     ref SDS 14 7455
362225 -      ..
362226 -     It would be useful to develop a few top levels of subjects, and to
362227 -     work on a process or set of rules for growing the system, as set
362228 -     out in the record on epistomology on 000311. ref SDS 16 0783
362229 -
362230 -        [On 000810 began thinking about universal subject management
362231 -        for SDS. ref SDS 55 0001
362233 -      ..
362234 -     It might also be helpful to provde some indication of cost savings
362235 -     from doing this work in order to encourage people to make the
362236 -     effort to learn how and to do it.  For example on 971008 USACE
362237 -     reported SDS subject management contributes to cost savings in the
362238 -     range of ROI 10:1 by reducing mistakes. ref SDS 9 1273
362239 -
362241 -  ..
362242 - Anchors Facilitate Linking to Establish Cause and Effect
362243 - DKR architecture 3-Layers - Information, Subjects, Search/Display
362244 - OHS/DKR Tool Collaborative, Evolutionary Epistomology
362245 -
362246 - On 000426 Jack explained need for architecture. ref SDS 22 0304
362247 -
362248 - Today, Jack cites discussion at SRI during the meeting yesterday that
362249 - proposed developing an engine that mutates original documents by
362250 - adding links to them. ref DRT 1 4725
362251 -
362252 -     This aligns with Doug's idea of adding anchors to archived email,
362253 -     and research papers, that facilitates citations, set as a vector
362254 -     on 000601. ref SDS 35 2760  It was proposed for the DKR Wiki
362255 -     system on 000609. ref SDS 42 6828
362256 -
362257 -        [On 010119 Doug sets presentation by engineer from Israel on
362258 -        linking without adding anchors to original sources on the web.
362259 -        ref SDS 63 945L
362261 -         ..
362262 -        [On 010122 BrowseUp offers technology that adds links to an
362263 -        original work, without permission of the author. ref SDS 64
362264 -        GHR2
362266 -         ..
362267 -        [On 010124 Jack cited risks from technology that enables other
362268 -        people to can add links to an original work. ref SDS 65 00FO
362270 -      ..
362271 -     LANL has a project with Xerox to accomplish this objective for
362272 -     archived documents, discussed on 000331. ref SDS 19 2405
362274 -  ..
362275 - Jack disagrees.  The architecture he presents in his letter today
362276 - permits no modifications of original documents. ref DRT 1 2891
362277 -
362278 -     This aligns generally with the explanation of a dynamic knowledge
362279 -     environment, set out on 000601. ref SDS 34 4968
362280 -
362282 -  ..
362283 - OHS/DKR Defined as...
362284 -
362285 -     Tool for collaborative evolutionary epistomology; everybody has
362286 -     the chance to contribute. ref DRT 1 8232
362287 -
362288 -        This supplements Eric Armstrong's idea for collaboration to be
362289 -        accomplished through email, proposed on 000505. ref SDS 25 4392
362290 -        It aligns with Doug Engelbart's goal to enhance collaboration
362291 -        for improving productivity, discussed during the Colloquium on
362292 -        000120, ref SDS 13 1640, and reviewed initially on 991222.
362293 -        ref SDS 11 0784
362294 -
362295 -           [On 000718 SRI pre-proposal to NASA does not offer technical
362296 -           capability for catagories nor ontology. ref SDS 54 2166
362298 -         ..
362299 -        The notion of a DKR limited to "collaboration" sows the seeds
362300 -        of its own destruction.  Dynamic knowledge requires a constant
362301 -        integration between thinking and doing, explained in POIMS.
362302 -        ref OF 1 2049  Collaboration is but a part of knowledge, and it
362303 -        depends on a wide range of other stuff, including the ability
362304 -        to roll over content into the daily work flow, using the record
362305 -        to guide action.
362307 -         ..
362308 -        Information Overload Solution Must Shove Paper into Computer
362309 -
362310 -        Jack mentioned the other day that his desk is cluttered with a
362311 -        lot of notes, papers, articles, and reminders that together
362312 -        cause information overload.  How will the collaborative
362313 -        evolutionary epistomology convert this information into useful
362314 -        knowledge, per discussion with Tom Keeling at USACE on 960418?
362315 -        ref SDS 7 8840
362317 -         ..
362318 -        We have to guard against the notion that we can add Jack's
362319 -        subjects to Eric's email to get "knowledge."  The goal is at
362320 -        once more complicated and more powerful, and it requires
362321 -        leveraging human thought, which takes front-end investment and
362322 -        hard work, cited on 000518. ref SDS 29 0017
362324 -         ..
362325 -        Below, Jack is thinking about an engine to assign subjects.  It
362326 -        will take quite a bit of thought to bring that off. ref SDS 0
362327 -        2915
362328 -
362329 -           [On 000710 received letter from Jack that needs front-end
362330 -           investment to create useful "knowledge." ref SDS 52 3961
362332 -            ..
362333 -           [On 000711 sent Jack a letter on this part of KM.
362334 -           ref SDS 53 9396
362336 -         ..
362337 -        Epistomology that evolves is a good idea.  Might be able to
362338 -        formulate a base line of top levels, and some rules to guide
362339 -        process of evolution.  On 000311 considered this idea.
362340 -        ref SDS 16 0783   Earlier on 000221 Jack cited challenge of
362341 -        organizing information. ref SDS 14 7455
362343 -         ..
362344 -        On 000331 developed ideas on this for LANL project. ref SDS 19
362345 -        9797
362346 -
362348 -  ..
362349 - 3-layer Architecture Proposed for OHS/DKR
362350 -
362351 - Follow up ref SDS 29 8439.
362352 -
362353 - Jack is working with Adam, Howard, and Peter Yim to create an ontology
362354 - in the B2B space. VerticalNet uses a carefully crafted ontology (on
362355 - which Howard works) to serve as an "interlingua" or, shall I say,
362356 - "page renderer", so that enterprises that have their own individual
362357 - ontology can be mapped onto the playing field. ref DRT 1 7575
362359 -  ..
362360 - The presentation Jack made with Marry Keeler at SRI on 000518 proposed
362361 - 3-layered architecture, ref SDS 29 C53G, and is mentioned in Jack's
362362 - letter again today. ref DRT 1 0989
362364 -  ..
362365 - Jack feels an architecture permits building an ontology that serves as
362366 - an interlingua to all possible users, ref DRT 1 7790, based on the
362367 - following three (3) primary categories...
362368 -
362369 -           [On 000710 Jack submits diagram of 3-layer architecture.
362370 -           ref SDS 52 V3YP
362372 -            ..
362373 -           [On 000710 received letter from Jack that needs front-end
362374 -           investment to create useful "knowledge." ref SDS 52 V3YP
362376 -            ..
362377 -           [On 001130 Jack submits analysis of SDS features to
362378 -           accomplish vision for 3-layer KM architecture. ref SDS 60
362379 -           5HW3
362381 -            ..
362382 -           [On 040709 3-layer architecture defined in POIMS for people,
362383 -           process, time. ref SDS 80 NG7H  Another 3-layer architecture
362384 -           needed for deployment that entails using existing tools
362385 -           without learning anything, using organizational memory to
362386 -           work intelligently, and using SDS to construct
362387 -           organizational memory in Knowledge Space. ref SDS 80 8M9N
362389 -            ..
362390 -           [On 040709 3-layer architecture defined in POIMS for people,
362391 -           process, time. ref SDS 80 NG7H  Another 3-layer architecture
362392 -           needed for deployment that entails using existing tools
362393 -           without learning anything, using organizational memory to
362394 -           work intelligently, and using SDS to construct
362395 -           organizational memory in Knowledge Space. ref SDS 80 8M9N
362397 -        ..
362398 -       Possibilities
362399 -
362400 -          All the "noise" out there, raw data, written/spoken discourse
362401 -          i.e., a database of human discourse, recorded experience.
362402 -          ref DRT 1 3127
362403 -
362405 -        ..
362406 -       Actualities
362407 -
362408 -          Mary calls this a "lense" (in her presentation at SRI on
362409 -          000518, ref SDS 29 2812), mapping possibilities into an
362410 -          ontology of structures that can be viewed, inferenced,
362411 -          debated; provides platform for reasoning and debate, and a
362412 -          permanent record of evolving human knowledge base.
362413 -          ref DRT 1 9603
362415 -             ..
362416 -            [On 000830 meeting reports OHS goal to provide a lens to
362417 -            view email archive. ref SDS 57 GO4J
362419 -             ..
362420 -            [On 001025 letter from Paul Fernhout relates Jack's ideas
362421 -            for building an engine that organizes information, perhaps
362422 -            constructing topic maps. ref SDS 58 IK5F
362424 -        ..
362425 -       Probabilities
362426 -
362427 -          What you and I do with the actualities.
362428 -
362429 -          Tools for finding, transcoding and displaying information
362430 -          according to momentary needs using ontology from Actualities.
362431 -          ref DRT 1 8439
362433 -  ..
362434 - This might be expressed differently to clarify understanding
362435 - as...
362436 -
362437 -   •  Information
362438 -   •  Ontology (subjects, epistomology, categories, key words, etc.)
362439 -   •  Search capability that displays information in multiple views
362440 -
362442 -  ..
362443 - How does Jack's search capability differ from Yahoo and other vendors
362444 - within the genre of "data mining" and "business intelligence" reviewed
362445 - on 980226. ref SDS 10 2146   For example, Jack often suggests using
362446 - Google.  How does the proposed search engine improve on Google?
362447 -
362449 -      ..
362450 -     Ontology Engine Proposed to Create and Map Subjects
362451 -
362452 -     Actually, Jack in point 2, below, expressly proposes a software
362453 -     program that develops and/or applies subjects to the record.
362454 -     ref SDS 0 2915
362455 -
362456 -
362458 -  ..
362459 - It would help to get a few scenarios comparing how people look up....
362460 -
362461 -          Ontology
362462 -          Ford Mercury
362463 -          Flowers
362464 -          Agriculture
362465 -          Knowledge Management
362466 -
362467 - ...on Yahoo.  Compare the process and results using Yahoo, with the
362468 - new DKR Jack proposes today.
362470 -  ..
362471 - Yahoo in particular has a structure for subjects that someone might
362472 - call an "ontology" or lens.  They are constantly adding subjects and
362473 - rearranging the thing, reflecting a dynamic environment.
362475 -  ..
362476 - Mere change does not make a subject management system adequately
362477 - "dynamic" nor sufficiently useful.
362479 -  ..
362480 - How will Jack's DKR improve on present practice, exemplified by Yahoo
362481 - discussed above?
362483 -  ..
362484 - How is this architecture used?
362485 -
362486 -    1.  Documents (e.g. articles, news items, books, papers, speeches,
362487 -        etc) are entered into the archive. ref DRT 1 2596
362488 -
362489 -        What does this mean?  What or where is the archive?  How does
362490 -        stuff get entered?  How much time does it take?  Who does it?
362492 -         ..
362493 -        What about phone calls, meetings, analysis, letters, -- we need
362494 -        a simple environment for assigning meaning, i.e., context,
362495 -        i.e., chronology, to everything
362496 -
362497 -
362498 -
362499 -
3625 -

SUBJECTS
Structured Information Tagged Topic Maps, Roy Roebuck, 000125
Knowledge Representation, Context Management
XML SGML Supports Atomic Data Structure Secret Knowledge Management
Topic Maps, Roy Roebuck, 000125
Structured Information, Roy Roebuck, 000125
Information Retrieval Reports Search Engine
Reporting Based on Subject Context
Map Ontology Organize Structure
AI Cannot Think No Biological Drives Cannot Map Human Experience
Engine AI Black Box Engine Mechanized Knowledge False Dangerous Idea
Ontology Engine, Jack Park

5613 -
561401 -  ..
561402 - Jack's letter to the OHS/DKR team continues...
561403 -
561404 -    2.  Engine is turned loose on archive to map topics for everything
561405 -        into the actualities layer. (as I said, whoever does this
561406 -        wins). ref DRT 1 5796
561407 -
561408 -        The "engine" seems aimed at creating the "ontology" of keywords
561409 -        that Jack described in his letter on 000221, ref SDS 14 7455,
561410 -        and further relates to Mary Keeler's presentation at SRI on
561411 -        000518 that explained a "lens" for filtering information.
561412 -        ref SDS 29 2812
561413 -
561414 -           [On 070511 created SDS support to automatically construct
561415 -           new accounts in the Subject Index based on people building a
561416 -           single template account, and automatically assign to Control
561417 -           Fields in SDS records. ref SDS 85 NU3J
561419 -         ..
561420 -        Jack recommended on 000602 that Ontologos has accomplished some
561421 -        or parts of this objective. ref SDS 39 8932  On 000607 this
561422 -        turned out to be a mistake.  There is no work product showing
561423 -        this can be done. ref SDS 40 0001
561425 -         ..
561426 -        On 911121 Morris explained an AI program that organizes the
561427 -        record automatically; turned out not to be useful for daily
561428 -        management. ref SDS 3 8809
561430 -         ..
561431 -        On 940603 Stanford reported on a technology development effort
561432 -        to create mediators for organizing the record, assisting expert
561433 -        librarians. ref SDS 4 8J6J
561435 -         ..
561436 -        On 000113 Ed Swanstrom with KMCI proposed a "black box" that
561437 -        accomplishes KM. ref SDS 12 3380
561438 -
561439 -            [On 080502 Kaiser reported that ordering medications from
561440 -            the pharmacy presents a "black box" of uncertain results
561441 -            filling prescriptions to treat patients. ref SDS 86 NM3M
561443 -         ..
561444 -        One problem with this proposal is that there is no task yet to
561445 -        create and maintain an "Ontology" or evolutionary Epistomology,
561446 -        as Jack calls it, that will be mapped by the "engine." Creating
561447 -        and maintaining subjects is a hard job, that requires skill.
561448 -        For example, on 000221 Jack notified the team that ontology is
561449 -        complex, like Pandora's Box. ref SDS 14 7455  On 000602 Jack
561450 -        reported that Ontologos was performing this work. ref SDS 39
561451 -        8932  On 000607 this understanding was determined to be a
561452 -        mistake. ref SDS 40 0001  Saying it will get done through
561453 -        collaboration overlooks the character of the job. Is there
561454 -        another engine to do this work?
561456 -         ..
561457 -        Actually, Jack may have something in mind here for the Topic or
561458 -        Graphical Map idea he proposed on 000403, ref SDS 21 1144, and
561459 -        earlier on 000331. ref SDS 20 2173
561461 -         ..
561462 -        On 960324 review of Landauer's LSA model showed correlations
561463 -        with SDS organic subject structure, which Jack's idea of an
561464 -        "engine" might support. ref SDS 6 8844
561465 -
561466 -           [On 000710 Jack formalizes architecture in a conceptual
561467 -           graph. ref SDS 52 0001
561469 -            ..
561470 -           [On 000710 received letter from Jack that needs front-end
561471 -           investment to create useful "knowledge," ref SDS 52 3961,
561472 -           per above. ref SDS 0 1116
561474 -            ..
561475 -           [On 000711 sent Jack a letter on this part of KM.
561476 -           ref SDS 53 9396
561478 -            ..
561479 -           [On 001025 received letter from Jack on using tools to
561480 -           create a representation without knowing its final use cases.
561481 -           You can then reach into that representation and construct
561482 -           useful views according to specific needs. ref SDS 58 LR6N
561484 -            ..
561485 -           [On 001121 MindSet is developing system to organize thoughts
561486 -           that may solve complexity issues. ref SDS 59 4G8G
561488 -            ..
561489 -           [On 001130 Jack proposes tools to navigate, ontology and an
561490 -           engine to create knowledge structures for SDS, ref SDS 60
561491 -           CC7K; noted none of this exists.
561493 -            ..
561494 -           [On 001219 project discussion shows values present complex
561495 -           challenge for organizing useful record. ref SDS 61 UM8M
561497 -            ..
561498 -           [On 001230 engineer seeking support to automate subject
561499 -           management. ref SDS 62 NW8R
561501 -            ..
561502 -           [On 010217 KM researcher associates SDS with AI-like search
561503 -           engine, Autonomy, explained in a Wired Magazine article
561504 -           which sounds similar to Jack's idea today. ref SDS 66 YL5F
561506 -            ..
561507 -           [On 010223 engine proposed for mining threads. ref SDS 67
561508 -           3RKS  None of this exists. ref SDS 67 N5RW
561510 -            ..
561511 -           [On 010321 POIMS explains two branches of KM. ref SDS 68
561512 -           0001
561514 -            ..
561515 -           [On 010405 Jack has a web site for a Nexist OHS project that
561516 -           shows a "Grove" engine in the architecture. ref SDS 69 485N
561518 -            ..
561519 -           [On 010425 Cycorp reports plans for Doug Lenat's team to
561520 -           release Knowledge Management work product building an
561521 -           ontology, ref SDS 70 GJ6J; and further to release an
561522 -           "inference" engine technology, which may meet Jack's
561523 -           requirements. ref SDS 70 079K
561525 -            ..
561526 -           [On 010614 analysis shows SDS organic subject structure may
561527 -           support KM better than an engine, until experience is gained
561528 -           that enables an engine to be designed that supports the
561529 -           architecture of human thought. ref SDS 71 HY6M
561531 -            ..
561532 -           [On 010620 SRI proposes an engine called NODAL to
561533 -           automatically Manage Distributed Multi-user Change Tracking
561534 -           that improves RDMS and CVS. ref SDS 72 0157
561536 -            ..
561537 -           [On 010730 DCMA expects KM will be an "engine" to process
561538 -           email. ref SDS 73 WK9K
561540 -            ..
561541 -           [On 010916 Eric Armstrong frustrated can't find anything in
561542 -           the record of work on OHS/DKR. ref SDS 75 KA6H  He reports
561543 -           SDS has amazing ability to find everything. ref SDS 74 0001
561545 -            ..
561546 -           [On 011003 Eric Armstrong frustrated information overload
561547 -           paralizes productivity; analysis hopeless quagmire; wants
561548 -           system to categorize. ref SDS 76 SW9L
561550 -            ..
561551 -           [On 020321 Kanisa reports progress organizing and
561552 -           classifying content to improve productivity of call centers
561553 -           where people get technical support. ref SDS 77 V79I
561555 -            ..
561556 -           [On 020729 Tom Munnecke raised the worry that engineers will
561557 -           devise a software engine to mine medical records for
561558 -           actionable scenarios, electronic ambulance chasing to drum
561559 -           up businss for lawyers. ref SDS 78 016K
561561 -            ..
561562 -           [On 020822 Microsoft Shearpoint describes search engine that
561563 -           crawls content to index metatadata into categories.
561565 -            ..
561566 -           [On 041208 Murray Altheim requests feedback on pilot testing
561567 -           his software project for organizing notes into different
561568 -           subjects that aid writing; a survey illustrates how to
561569 -           engage customers in paying attention to Cyerle for
561570 -           supporting tasks people care about. ref SDS 81 P67J
561572 -            ..
561573 -           [On 060211 SRI CALO and Iris project reports progress
561574 -           developing an "ontology engine." ref SDS 82 TE6F
561576 -            ..
561577 -           [On 060527 Jack recommended IEML website to illustrate using
561578 -           subject maps and topic maps; review shows why KM is a lot of
561579 -           hard work. ref SDS 83 EV5Q
561581 -            ..
561582 -           [On 060907 commend Jack's work and commitment to advance
561583 -           knowledge management using topic maps. ref SDS 84 IH6O
561585 -            ..
561586 -           [On 070511 context management constructs multiple
561587 -           accounts with organic structure in Subject Index, and
561588 -           assigns to Control Fields in SDS records for finding
561589 -           specific details, and assembling multiple views for trend
561590 -           analysis to support decision support and continual
561591 -           learning. ref SDS 85 0001
561593 -         ..
561594 -        Given the organic and fluid character of subjects, how will an
561595 -        engine match subjects to content? ref OF 1 0561  Jack cited
561596 -        this dilemma in his letter to the Colloquium on 000221.
561597 -        ref SDS 14 7455  More recently on 000331 LANL proposed speech
561598 -        pattern matching capability to develop subjects by interpreting
561599 -        information. ref SDS 19 9797
561601 -           ..
561602 -          [On 001130 noted pending action item from this record.
561603 -          ref SDS 60 QD5F
561605 -         ..
561606 -        Developing intelligent agents or "engines" as Jack proposes
561607 -        today seems to require the "mediators" discussed by the folks
561608 -        at Stanford on 940603. ref SDS 4 0786  Such efforts have not
561609 -        been successful.
561610 -        ..
561611 -        What might be done is to provide some high level
561612 -        categories, but this is already being done.  What will be done
561613 -        differently by the DKR engine?
561615 -         ..
561616 -    3.  User constructs a view into actualities, perhaps as a query,
561617 -        perhaps as a simple mapping of the knowledge structures
561618 -        contained in actualities to a topic map, for which templates
561619 -        may be available. ref DRT 1 6916
561620 -
561621 -          Is the proposal to open a subject index with structures that
561622 -          help frame a query based on related and alternate context?
561623 -          That capability is very useful.
561625 -         ..
561626 -        It doesn't really stop there.  Let's pretend user takes
561627 -        exception with something discovered in actualities.
561628 -
561629 -          [On 010916 Eric Armstrong reports Eugene Kim has developed
561630 -          dialog map capability that sound similar to topic maps for
561631 -          organizing the record. ref SDS 75 S44G
561633 -           ..
561634 -          [On 010916 Eric reports it takes a lot of time to construct a
561635 -          dialog/topic map. ref SDS 75 4J4J
561637 -         ..
561638 -    4.  User opens a "debate" view after selecting a particular
561639 -        actuality item (node?), ref DRT 1 9064
561641 -         ..
561642 -    5.  DKR creates a new document in possibilities to record the
561643 -        nature of the criticism. ref DRT 1 3300
561645 -         ..
561646 -    6.  DKR alerts subscribers to the debate. ref DRT 1 4161
561648 -         ..
561649 -    7.  DKR maps new document into actuality. ref DRT 1 4836
561650 -
561652 -  ..
561653 - Ideas 3 - 7 don't sound helpful.
561655 -  ..
561656 - Need ability to customize the thing at a level of organization,
561657 - department, division,... person.
561658 - ..
561659 - People don't want a debate.  They have work to do.
561661 -  ..
561662 - They want to create a path to assemble stuff in a way that discloses
561663 - important patterns that are otherwise obscured by information
561664 - (possibilities), then they want to go to the next meeting, send an
561665 - email or go home, or catch a plane to Japan.
561667 -      ..
561668 -     Communication Manager Masters Beads
561669 -     Flexible, Personal Ownership v. Official Reliable Record?
561670 -
561671 -     Jack concludes from points 3 - 7 that user does NOT have write
561672 -     access to actuality.  Only the system does -- and that, of course,
561673 -     is the big issue here.  Hesse's Glass Bead Game suggested that
561674 -     there is a Bead Master, one individual that has the ability to do
561675 -     such mappings and control the flow of the epistemological
561676 -     evolution within the system.  I tend to think that will not
561677 -     happen, at least in my lifetime.  There needs to be a "machine"
561678 -     that does this work, and there is an enormous body of scholarly
561679 -     work being generated that hints of the emergence of this
561680 -     capability. ref DRT 1 2580
561681 -         ..
561682 -         This sounds like Ted Nelson's idea of a permenant
561683 -         address for information in Knowledge Space, for everyone; the
561684 -         idea was reviewed on 000305, ref SDS 15 7733
561686 -          ..
561687 -         That may not be what Jack has in mind, but it sounds like it.
561689 -          ..
561690 -         Problems of confidentiality and bumbling augur against this
561691 -         approach.
561693 -          ..
561694 -         Communication Managers, like scribes in earlier times, help
561695 -         people develop the record.  A new function that scribes did
561696 -         not perform is to maintain an organic subject structure, that
561697 -         accomplishes the "lens" function Jack mentions, ref SDS 0
561698 -         0750, and was explained by Mary Keeler at SRI on 000518.
561699 -         ..
561700 -         The explanation of a Bead Master sounds like a
561701 -         comptroller to manage filing and forms that provide uniform
561702 -         communications, similar to accountants who control finances.
561703 -         ..
561704 -         This is an area that needs careful consideration because
561705 -         people are members of organizations, as well as individuals.
561707 -          ..
561708 -         The first purpose of the entire exercise is to augment human
561709 -         intelligence.  That in turn improves the work, including
561710 -         collaboration, which improves earnings and solves world
561711 -         problems.
561713 -          ..
561714 -         Augmenting human intelligence requires converting information
561715 -         into knowledge using the tools operating on the record.
561716 -         Therefore, the record is a continuous information stream owned
561717 -         and controlled by the originator.
561719 -          ..
561720 -         Each individual alone has write access to their stuff.
561721 -         ..
561722 -         Each individual is responsible for selecting which part
561723 -         of their stuff is released to whom, including the organization
561724 -         paying the bills, in the same way that people who hear and see
561725 -         things choose which part of their experience to share with
561726 -         others.
561727 -         ..
561728 -         Something needs to be worked out on how stuff gets
561729 -         released into the official record.  What makes something
561730 -         official that can be relied upon, as opposed subject to change
561731 -         by anyone? That is the big issue?
561733 -          ..
561734 -         This is the engineering management problem discussed by Eric
561735 -         on 000614, ref SDS 44 0895, based on work from 000609 setting
561736 -         up the Wiki DKR site. ref SDS 42 4588
561738 -          ..
561739 -         The problem we get into is that it takes a lot of work to
561740 -         manage subjects.  The hope that a machine will do this seems
561741 -         remote, at best.
561742 -
561744 -  ..
561745 - Questions on Architecture...
561746 -
561747 - Jack submits a good analysis of KM potential, i.e., the "vision"
561748 - aspect of architecture, ref SDS 0 5475, which he identified on 000426.
561749 - ref SDS 22 0304  The vision seems limited to subject management, which
561750 - is only part of KM.  How will this method provide a "dynamic"
561751 - environment for improving daily work that can solve world problems,
561752 - explained during the meeting at Intel on 000517. ref SDS 28 7227
561754 -  ..
561755 - A big preliminary requirement is a conceptual graph or flow chart
561756 - showing how the pieces fit together.
561758 -  ..
561759 - Jack does not discuss...
561761 -  ..
561762 -
561763 -     a.  Knowledge definition implemented by his architecture, and how
561764 -         this can accomplish "knowledge management."  On 000516 Jack
561765 -         submitted a formal definition of knowledge that is too sterile
561766 -         to guide development of tools. ref SDS 27 4723
561767 -
561768 -         How does Jack's architecture relate to definition in the
561769 -         project glossary, received on 000601. ref SDS 37 6951
561770 -
561771 -            ...with meeting at Intel on 000517? ref SDS 28 0785
561772 -
561773 -            ...with record of Mary's talk at SRI on 000518? ref SDS 29
561774 -            8439
561775 -         ..
561776 -         How will this new capability differ from current
561777 -         practice, per above. ref SDS 0 1998 and ref SDS 0 0490
561779 -  ..
561780 -
561781 -     b.  Level of effort, process and tools to generate and maintain
561782 -         an organic subject structure.
561784 -  ..
561785 -
561786 -     c.  Integrating time and information to understand causation and
561787 -         manage complexity.
561789 -  ..
561790 -
561791 -     d.  Alignment to discover gaps in facts and reasoning in time to
561792 -         maintain course, as related by Morris on 950303. ref SDS 5
561793 -         3497
561795 -  ..
561796 -
561797 -     e.  Machines cannot do alignment because they lack Baker Street
561798 -         reasoning to look beyond their instructions.
561800 -  ..
561801 -
561802 -     f.  Integrating tasks to form a single new task of "intelligence,"
561803 -         or if people prefer, knowledge management, set out in POIMS.
561804 -         ref OF 1 2688
561806 -  ..
561807 -
561808 -     g.  Summary linked to detail
561809 -
561810 -     h.  Skills in preparing analysis and meaningful summaries
561811 -
561812 -         This requires an educational and transitioning effort.
561814 -  ..
561815 -
561816 -     i.  Notice and feedback
561817 -
561818 -         Requires diplomatic skills, leadership and courage.
561820 -  ..
561821 -
561822 -     j.  Emotional burdens of constant exposure to error and resistance
561823 -         to discovery, explained in NWO...
561824 -
561825 -         Requires dedicated assignment to do the work, otherwise it
561826 -         will not get done.
561828 -  ..
561829 -
561830 -     k.  DKR under Jack's architecture seems to organize information
561831 -         that is "outside" in books, articles and so on, like a giant
561832 -         encyclopedia.
561833 -
561834 -         This is the notion that "intelligence" is held by others.
561836 -          ..
561837 -         What about discovering our own "intelligence" and improving
561838 -         the management of that resource?
561840 -          ..
561841 -         There is no discussion in Jack's architecture of aiming the DKR
561842 -         technology at the bulk of knowledge people need for doing
561843 -         their daily work which comes from their personal thinking,
561844 -         attending meetings, making phone calls, informal discussion,
561845 -         all as cited by Doug in his 1972 paper, reviewed on 000327.
561846 -         ref SDS 17 3971
561848 -  ..
561849 -
561850 -     l.  OHS, CDS need correlation; Eric's specs can be spruced up to
561851 -         accomplish ontology function, or is Jack thinking of a much
561852 -         different process that eliminates OHS?   Eric added categories
561853 -         in v0.7 received on 000601. ref SDS 36 5933
561854 -
561855 -      [On 000624 sent letter to Mary Keeler on KM. ref SDS 49 1534
561857 -       ..
561858 -      [On 000627 called Jack to follow up. ref SDS 50 0001
561859 -
561860 -
561861 -
561862 -
561863 -
561864 -
561865 -
561866 -
561867 -
561868 -
5619 -