Click here to comment!
1...What the hell is [a DKR]? ref DRT 1 3540
CONTACTS
SUBJECTS
Use Case Method Define Requirement,
Architecture, DKR, 000423
Park SDS Demonstrates Proof of Concept DKR, 000426
Archiecture DKR Needed, 000426
Purpose DKR
DKR Needs Architecture, 000426, Jack Park
Architecture Vision, Marketing, Engineering
DKR Architecture Vision, Marketing, Engineering
DKR Difficult Architecture, Hard to Design, Not Understood
1311 -
1311 - ..
1312 - Summary/Objective
1313 -
131301 - Follow up ref SDS 29 0005, ref SDS 28 4933.
131302 -
131303 -
131304 -
131305 -
131306 -
131308 - ..
1314 -
1315 -
1316 - Progress
131701 - ..
131702 - Architecture Combines Marketing, Engineering, Vision
131703 -
131704 - Follow up ref SDS 29 0005, ref SDS 28 4933.
131705 -
131706 - Received ref DRT 1 0001 from Jack explaining architeture is the 1st
131707 - level design stage that guides overall development.
131709 - ..
131710 - Architecture delineates categories of components and their
131711 - interrelationships.
131712 -
131713 - Category level
131714 -
131715 - Can draw from the many studies of design patterns.
131717 - ..
131718 - Class level
131719 -
131720 - Dives inside each category and fleshes out just how
131721 - things should actually look and communicate.
131723 - ..
131724 - In UML methodology, ref DRT 1 4758, you define...
131725 -
131726 - Categories (equivalent to Java packages), then do a...
131727 -
131728 - Sequence diagram on those categories as a means of
131729 - fleshing out the use cases (scenarios). Once you know
131730 - that something in category A needs to send some highlevel
131731 - message to category B, then you begin to visualize the
131733 - ..
131734 - Classes and methods inside the categories that will carry
131735 - out the gestalt of the message. So, you next plan your
131736 - classes, using class/method-level sequence diagrams to
131737 - flesh out whole scenarios in detail, inventing messages
131738 - and methods as you go.
131739 -
131741 - ..
131742 - Architecture = Vision, Marketing Needs, Engineering Capabilities
131743 - Needs Continual Alignment, Key to Augment Intelligence
131744 -
131745 - Jack explains daily work should draw from original narrative
131746 - setting the architecture, ref DRT 1 3330, based on combined works
131747 - of...
131748 -
131749 - • vision (what folks want to get done).
131751 - ..
131752 - • marketing (what the market thinks it wants),
131754 - ..
131755 - • engineering (what folks think can be done), and
131757 - ..
131758 - [On 000518 Doug Engelbart requested glossary of terms to
131759 - guide architecture based on definition of "knowledge" and
131760 - "knowledge management." ref SDS 41 3286
131762 - ..
131763 - [On 001017 Eric Armstrong developing source code along with
131764 - an architecture that makes sense. ref SDS 49 0001
131766 - ..
131767 - Requirement for daily work to draw from "original narrative"
131768 - applies ISO criteria calling out traceability to original sources,
131769 - reviewed on 950721, ref SDS 4 1740. This capability is summarized
131770 - by the POIMS concept of alignment, ref OF 1 3774, as a key part of
131771 - intelligence. Alignment reduces "meaning drift," explained on
131772 - 991101, ref SDS 11 2800, which otherwise causes continual bumbling
131773 - in technology, medicine, ref DIP 1 0001, construction, education,
131774 - government, everywhere, under Aristotle's rule, ref OF 2 4564,
131775 - which makes...
131777 - ..
131778 - Communication the biggest risk in Enterprise
131780 - ..
131781 - Thus, the design process inherently requires SDS capability to
131782 - augment human intelligence, called out by Eric as the purpose of
131783 - the DKR on 000423. ref SDS 28 5096
131784 -
131786 - ..
131787 - Vision of DKR Vast and Inspiring to Solve World Problems
131788 - DKR Undefined for Accomplishing Vast Vision
131789 -
131790 - Thus far, Doug has elucidated a rather vast and huge picture of
131791 - what needs to be done (his vision) -- e.g., improving improvement,
131792 - ABC method, intelligence collection, reported on 991222,
131793 - ref SDS 13 3961, but has not yet drilled down to the bloody details
131794 - of what that should look like.
131796 - ..
131797 - Right now, we know we want a dynamic knowledge repository.
131799 - ..
131800 - What the hell is [a DKR]? ref DRT 1 3540
131802 - ..
131803 - Jack's focus on defining the DKR, reflects Eric Armstrong's point
131804 - responding to Adam Cheyer on 000423 indicating the OHS is not
131805 - defined, ref SDS 29 5880, set out previously on 000120. ref SDS 14
131806 - 5063
131807 -
131808 - [On 000503 Eric Armstrong advises "knowledge" and KM are
131809 - difficult to grasp in desiging a DKR. ref SDS 35 5033
131811 - ..
131812 - [On 000503 Jack cites Knowledge Space. ref SDS 35 6138
131814 - ..
131815 - [On 000504 Eugene Kim submits good explanation of features or
131816 - use cases for DKR and OHS. ref SDS 37 6082
131818 - ..
131819 - [...Doug Engelbart reports NSF rejected proposal because it
131820 - failed to define Knowledge Management. ref SDS 38 5555
131822 - ..
131823 - [On 000505 Eric submits spec for OHS/DKR v0.5 that does not
131824 - align with architecture provided today, including objective
131825 - to augment human intelligence, set by Eric on 000423.
131826 - ref SDS 39 0375
131828 - ..
131829 - [On 000505 Eric proposes improving email to begin forming an
131830 - architecture to augment intelligence with an OHS/DKR.
131831 - ref SDS 39 4392
131833 - ..
131834 - [On 000517 Eric advises again wants to defer working on DKR
131835 - because "knowledge" is difficult to design tools. ref SDS 40
131836 - 5092
131838 - ..
131839 - [On 000615 DKR team at SRI deferring work on DKR because
131840 - "knowledge" is not well understood. ref SDS 44 6271
131842 - ..
131843 - [On 001025 Doug submits OHS Launch Plan that mentions DKR.
131844 - ref SDS 50 C9WP
131846 - ..
131847 - DKR Delivers Intelligence in Knowledge Space Anytime, Anywhere
131848 -
131849 - POIMS offers a design path for shifting the paradigm of
131850 - augmenting human intelligence, supported by Eric on 000423,
131851 - ref SDS 28 5096, from traditional reliance on "documents," to
131852 - the new medium of Knowledge Space, explained in POIMS,
131853 - ref OF 1 1107, and discussed on 000424 formulating the purpose
131854 - of the DKR. ref SDS 29 4833
131856 - ..
131857 - Knowledge Space was defined on 960620. ref SDS 5 3516
131858 -
131859 - [On 000503 Jack cites Knowledge Space. ref SDS 35 6138
131860 -
131861 - [On 000504 Jack suggests pondering POIMS. ref SDS 37 6082
131862 -
131863 - [On 001105 objection to Knowledge Space. ref SDS 51 AE7L
131864 -
131866 - ..
131867 - Marketing Focused on What Can Be Explained in 30 Seconds
131868 - Eric Focusing on Marketing, What Market Thinks it Wants
131869 -
131870 - On 000423 Eric showed need to explain project purpose concisely
131871 - to draw interest and further inquiry from investors...
131872 -
131873 - 1. Augment human intelligence, ref SDS 28 5933
131875 - ..
131876 - 2. Tool to record decisions and rationales so that knowledge
131877 - gained can be applied to future projects.
131879 - ..
131880 - [On 000503 Eric notes help is needed on defining "knowledge."
131881 - ref SDS 35 5033
131883 - ..
131884 - [On 000505 Eric submits spec v0.5 that does not align with
131885 - architecture provided today, including objective to augment
131886 - human intelligence, set by Eric on 000423. ref SDS 39 0375
131888 - ..
131889 - On 000212 Eric proposed an innovation for technology that augments
131890 - human memory. ref SDS 15 9790 On 000424 Eric explained need to
131891 - narrowly focus the project on things to build that can be explained
131892 - to investors. ref SDS 29 0037
131893 -
131894 - 3. Improve email, set out on 000423, as an actual deliverable
131895 - the project team understands at this time, ref SDS 28 5943
131896 - answering Jack's question, per above. ref SDS 0 4940
131898 - ..
131899 - This record supports analysis on 000425, ref SDS 31 0480, showing
131900 - knowledge management is not as easy as 1 2 3. People can get this
131901 - point, or that point, but not be able to get the strategic third
131902 - leg that makes KM work. POIMS uses the ideas of people, process and
131903 - time. ref OF 1 5884
131904 -
131905 -
131906 -
1320 -
SUBJECTS
SDS Proof of Concept Knowledge Management Intelligence Support Expla
3303 -
330401 - ..
330402 - Proof of Concept for DKR, Knowledge Space Provided by SDS
330403 - Engineering What Can Be Accomplished, Augment, SDS, LifeStreams
330404 - SDS, Augment LifeStreams Demonstrate Proof of Concept
330405 -
330406 - Jack notes that Doug's Augment NLS program sets the stage for
330407 - implementing a vision for KM, per above. ref SDS 0 2340 Rod Welch
330408 - brings a proof of concept for some aspects of a DKR, ref DRT 1
330409 - 3245, per report by Jack previously on 000405 asking the OHS/DKR
330410 - team to review SDS. ref SDS 23 2928
330411 -
330412 - On 000227 Dick Karpinski reported SDS is the best personal DKR
330413 - in daily use. ref SDS 17 0897
330415 - ..
330416 - On 000407 Doug was notified about report from US Army Corps of
330417 - Engineers citing SDS for adding "intelligence" to daily
330418 - management, saving time and money. ref SDS 24 0001
330419 -
330420 - [On 000428 thanked Jack for noticing Welch work. ref SDS 32
330421 - 0001
330423 - ..
330424 - [On 000503 Eric notes that help is needed on defining
330425 - "knowledge." ref SDS 35 5033
330426 -
330427 - [On 000517 met with Eric and Morris at Intel to define
330428 - knowledge set vision of Knowledge Management. ref SDS 40
330429 - 0001
330431 - ..
330432 - [On 000518 "knowledge" defined again during meeting at SRI
330433 - on DKR project. ref SDS 41 3528
330435 - ..
330436 - [On 000503 Jack cites Knowledge Space. ref SDS 35 6138
330438 - ..
330439 - [On 000504 Jack Park complains to OHS/DKR team struggling to
330440 - formulate a design for Knowledge Management has ignored SDS,
330441 - and foundational documents as "things we don't talk about
330442 - around here," and noted requirements to ponder SDS in order
330443 - to accomplish project objectives. ref SDS 37 XD5M
330445 - ..
330446 - [On 000504 Jack and Eugene Kim commend SDS for DKR methods.
330447 - ref SDS 37 6082
330449 - ..
330450 - [On 000601 funding requires proof of ability to perform,
330451 - avoid high tech tourism. ref SDS 42 1007
330453 - ..
330454 - [On 000613 Paul Fernhout commends SDS to DKR team.
330455 - ref SDS 43 0001
330457 - ..
330458 - [On 000622 Augment video reviewed. ref SDS 45 9626
330460 - ..
330461 - [On 000922 Jack baffled about why people have not addressed
330462 - SDS foundational documents, POIMS, NWO, Typical Day Scenario,
330463 - even if they do not try SDS, ref SDS 48 016R; he feels peer
330464 - pressure may be a factor; people feel funny "going first" to
330465 - cite authority for ideas for Knowledge Management that nobody
330466 - else has presented. ref SDS 48 FJ5H
330468 - ..
330469 - [On 000824 Eric Armstrong relates meeting on architecture of
330470 - OHS email management program based on SDS. ref SDS 47 PU5N
330472 - ..
330473 - [On 001116 Jack tells project team that SDS is amazing
330474 - technology that proves KM is possible. ref SDS 52 0001
330476 - ..
330477 - [On 001130 Jack reports SDS has the underlying structure and
330478 - the right interface for KM. ref SDS 53 H17O
330480 - ..
330481 - [On 020217 Gary Johnson cites SDS as proof of existence.
330482 - ref SDS 54 9F4J
330484 - ..
330485 - Jack Park continues...
330486 -
330487 - David Gelernter (another visionary) has brought to the table
330488 - another existence proof of concept (LifeStreams) which has some
330489 - fundamental similarities to Rod's work. ref DRT 1 1887
330490 -
330491 - [On 000710 Jack cites article by Gelernter proposing time is a
330492 - useful organizing method. ref SDS 46 3961
330494 - ..
330495 - [On 031215 Gary Johnson provided Gelertner's explanation of
330496 - Lifestreams. ref SDS 55 0001
330498 - ..
330499 - [On 070126 Freeman, author of Lifestreams phd paper,
330500 - explains subsequent consideration of using powerful new
330501 - search tools based on "google" design to help find things
330502 - in data structures for common storage based on time,
330503 - chronology, diary. ref SDS 56 167G
330505 - ..
330506 - Doug Lenat has demonstrated existence proof of the concept of
330507 - evolutionary epistemology (Eurisko), and VerticalNet, the company
330508 - for which I work, is generating proof of the need for and value of
330509 - ontological engineering (the study of what is) at the bottom of
330510 - everything. And under that lies knowledge representation (Erics
330511 - atomic structures).
330513 - ..
330514 - On 000221 Jack submitted research showing that organizing information
330515 - into useful knowledge is a complex task. ref SDS 16 3248 At that
330516 - time, background was submitted to help the OHS/DKR team meet this
330517 - challenge. ref SDS 16 M854 More recently, on 000307 further research
330518 - by OHS/DKR team found that knowledge management is a lot of hard work
330519 - using popular information technology. ref SDS 18 5362
330521 - ..
330522 - On 000331 Jack submitted an article by Gelertner's work. ref SDS 22
330523 - 0748
330525 - ..
330526 - Jack continues...
330527 -
330528 - My gosh! Parts of a DKR are already up and running in one form or
330529 - another out there. It remains for us, as I think Doug has asked, to
330530 - describe just what goes into a DKR, and go build it. ref DRT 1 DB5F
330531 -
330532 -
330534 - ..
330535 - Jack recommends...
330536 -
330537 - Mine Rod's web site, his technology white papers and so forth, mine
330538 - Gelernter's work, look at Lenat's work, look around, and formulate
330539 - a final narrative that everyone can agree adequately lays out the
330540 - vision, the market, and the technology available to us. ref DRT 1
330541 - 1353
330542 -
330543 - [On 000710 Jack cites article by Gelernter proposing time is a
330544 - useful organizing method. ref SDS 46 3961
330545 -
330546 -
330547 -
330548 -
330549 -
3306 -
SUBJECTS
Use Case Method Define Requirement,
Park, Jack
Architecture, DKR, 000423
Transcoding, e.g., WBI, IBM
WBI Transcoding, IBM, 000324
Transcoding, 000413
3908 -
390901 - ..
390902 - WBI Implements Design After Architecture, May Not be Adequate
390903 -
390904 - Jack notes that work on WBI jumps deeply into implementation issues;
390905 -
390906 - Doug considers Transcoding rather central to the whole system and
390907 - worthy of "jumping ahead" to mess with. In the end, WBI may not
390908 - statisfy our needs for open source or cross platform capability; there
390909 - are other approaches to the Transcoding solution. ref DRT 1 3744
390910 -
390911 -
390912 -
390913 -
3910 -
SUBJECTS
Agenda Issues
4003 -
4004 - 2217 received letter from Eric
400501 - ..
400502 - Agenda Issues Pending for Discussion
400503 -
400504 - Received ref DRT 2 0001 from Eric submitting an update on the agend
400505 - for project meetings from his submission on 000407. ref SDS 24 3648
400506 -
400507 - Doug is planning to present Augment. ref DRT 2 5544
400509 - ..
400510 - WBI from above, ref SDS 0 2800, is planned. ref DRT 2 4324
400512 - ..
400513 - Architecture from above, ref SDS 0 0005, is planned. ref DRT 2 0976
400514 -
400515 - "Starter Technologies" that do some DKR stuff, per Jack above.
400516 - ref SDS 0 3315, requires review for Doug's trip to Washington.
400517 - ref DRT 2 1005
400518 -
400519 - jack cites SDS supports some DKR features. ref SDS 0 3315
400521 - ..
400522 - [On 000503 Eric advised of DKR starter ideas being considered.
400523 - ref SDS 36 4004
400525 - ..
400526 - License and Business Model is planned. ref DRT 2 0891, reflecting
400527 - review on 000407. ref SDS 24 6973
400528 -
400529 - On 000423 this issue has begun to get attention. ref SDS 28 0784
400530 -
400531 - On 000424 Eric cited need for focus on what to build. ref SDS 29
400532 - 0037
400533 -
400535 - ..
400536 - Agenda Issues Not Scheduled include...
400537 -
400538 - How will DKR solve world problems. ref SDS 24 6554
400539 -
400540 - This may be an ABC presentation by Doug, but then we have to
400541 - tie to mission, architecture and then to nuts and bolts.
400543 - ..
400544 - Knowledge definition, including intelligence.
400545 -
400546 - Predicate to architecture.
400548 - ..
400549 - Pandora's Box of Too Much Knowledge.
400550 -
400551 - Predicate to how world problems are solved and created.
400553 - ..
400554 - Ongologies, organic subject structures
400555 -
400556 - Follows architecture.
400557 -
400558 -
400559 -
400560 -
400561 -
400562 -
400563 -
400564 -
4006 -