Click here to comment!
1...This section below is repetitious; would work to drop
CONTACTS
0201 - Armstrong Consulting 650 845 1782
020101 - Mr. Eric Armstrong
020102 - eric.armstrong@eng.sun.com
0202 - Eugene Eric Kim 650 330 1381
020201 - Mr. Eugene Eric Kim
020202 - eekim@eekim.com
SUBJECTS
OHS/DKR Progress Announcement Soon by Eugene Kim, per Eric Armstrong
FAQ-index into an Argument, Eugene Kim's Work, Review by Eric Armstro
Organizational Memory Knowledge Repository History, Experience, Lesso
Engine Create Topic Map Dialog Map Organize Navigate Record
Search Engine Apply Topic Map Assemble Record Find Information
Tricky Procedures Play DKR for Wiki, Risky, 000614
Engineers Don't Want to Play DKR Do Engineering Management, 000614
Pilot Test Existing Capability, Start with What is Available, 000302
OHS Launch Community Started by Eugene Kim Invites Contributors
Anchors Email Provided by Dialog Mapping, Eugene Kim
2412 - ..
2413 - Summary/Objective
2414 -
241401 - Follow up ref SDS 61 0000, ref SDS 60 0000.
241402 -
241403 - Apologized for strong remarks on 010917. Eugene provided an address
241404 - to review work on dialog mapping for the OHS Community Launch
241405 - initiative he has underday. Review indicates this is in formative
241406 - stages of identifying capabilities for intelligence that save time and
241407 - money. Needs specific approach for ontology and other aspects of
241408 - Knowledge Space.
241409 -
241410 -
241411 - This is a test. ref SDS 63 0001
241412 -
241413 -
241414 -
241415 -
241416 -
241417 - ..
2415 -
2416 -
2417 - Progress
2418 -
241801 - ..
241802 - OHS Launch Community Initial Application for Dialog Maps
241803 - Pilot Test Dialog Maps Organize Email for OHS Launch Community
241804 - Dialog Maps Limited to Index OHS Launch Comm for Pilot Test
241805 -
241806 - Follow up ref SDS 61 S44G, ref SDS 60 S44G.
241807 -
241808 - Called Eugene to apologize for stridancy in the letter on 010917, per
241809 - below. ref SDS 0 I58K
241810 -
241811 - Asked for example of dialog maps he has done so far?
241812 -
241813 - Eugene provided an address per below. ref SDS 0 NX6N
241814 -
241815 - He confirmed that dialog mapping is applied so far to managing email.
241816 - ..
241817 - Eugene advised there is no....
241818 -
241819 - Codifying mechanism used for dialog maping email which Eric
241820 - mentioned in his report on 010916. ref SDS 60 6O6I There is no
241821 - mention of an ontologist, although Eugene would initially fill
241822 - that role by default.
241823 -
241824 - Examination of work product, per below, so far shows no method of
241825 - organization nor retrieval of context, nor chronology, nor
241826 - summary, nor action items, nor anything but rudimentary linking
241827 - to email. ref SDS 0 NX6N
241828 -
241829 - Ontology is discussed only in relation to NODAL, and merely sets
241830 - an agenda to work on this at some time in the future. ref SDS 0
241831 - XJ8F
241832 -
241833 -
241834 -
241835 -
241836 -
241837 -
241838 -
241839 -
2419 -
SUBJECTS
OHS Launch Community Started by Eugene Kim
Addressability Anchors Added During Translation
Email Addressability Provided by Dialog Mapping, Eugene Kim
OHS Launch Community Started by Eugene Kim Invites Contributors
2807 -
280701 - ..
280702 - OHS Launch Community New Group
280703 -
280704 - Follow up ref SDS 61 00UU.
280705 -
280706 - Eugene explained there is an Internet location for the OHS Launch
280707 - Community that he has started, as reported in his letter on 010917.
280708 -
280709 - Procedure for opening the site is to first open.....
280710 -
280711 - Eugene Eric Kim
280712 -
280713 - http://www.eekim.com/
280714 -
280715 - This has a paragraph of narrative that begins: "I'm a freelance
280716 - writer and consultant....." The second line has a link to....
280717 - ..
280718 - Open Hyperdocument System Launch Community
280719 -
280720 - Click on this link and it opens.....
280721 -
280722 - ..
280723 -
280724 - OHS Launch Community
280725 -
280726 - http://www.eekim.com/ohs/lc/index.html
280727 -
280728 - Eugene explained we see an example of a dialog map he has done
280729 - for some email traffic by clicking on
280730 -
280731 - Discussion
280732 -
280733 - ...in the series of optiions near the top of the page, and just
280734 - above the title line (OHS Launch Community) that says....
280735 -
280736 - ..
280737 - Launch Community Ontology Library Discussion Members
280738 - ----------
280739 -
280740 - This opens a location that says...
280741 -
280742 - ..
280743 -
280744 - Discussion
280745 -
280746 - http://www.eekim.com/ohs/lc/discuss.html
280747 -
280748 - Meetings
280749 -
280750 - We meet periodically at SRI in Menlo Park, California to pick
280751 - Doug's brain and to discuss each other's projects. We are
280752 - currently experimenting with the IBIS methodology using The Soft
280753 - Bicycle Company's QuestMap software to help facilitate and record
280754 - the contents of meetings
280755 -
280756 - There is a list of items beginning on June 14, 2001 and continuing to
280757 - August 9, 2001.
280758 - ..
280759 - There is also a section.....
280760 -
280761 - Online
280762 -
280763 - We also collaborate via e-mail. While our mailing list is closed
280764 - for participation, anyone may view our list's
280765 - granularly addressable archives. (09)
280766 -
280767 - I've been experimenting with maintaining a dialog map of e-mail
280768 - conversation, with links to the actual e-mails. The results for
280769 - our first month of discussion is available in HTML and graphically
280770 - (PNG).
280771 -
280772 - ..
280773 -
280774 - Clicking on HTML in the last line goes to work so far on system Eugene
280775 - explained in his letter on 010917. ref SDS 60 S44G
280776 -
280777 -
280778 - Dialog Mapping
280779 -
280780 - ohs-lc@bootstrap.org Dialog Map
280781 -
280782 -
280783 - http://www.eekim.com/ohs/lc/dialogmaps/ohs-lc.html
280784 -
280785 -
280786 - This is an outline of issues with links to information from email
280787 - submitted by the folks invited by Eugene to contribute on the OHS
280788 - Launch Community.
280789 - ..
280790 - It looks similar to the outline below for the PNG diagram.
280791 - ref SDS 0 HS5H
280792 - ..
280793 - As Eugene explained above, there is no codifying system for
280794 - organizing, which Eric mentioned in a letter on 010916,
280795 - ref SDS 60 S44G, retrieving and assembling the record, nothing for
280796 - summarizing, nothing that imparts cause and effect. ref SDS 0 PJ6J
280797 -
280798 -
280799 - Clicking on PNG goes to flow chart.....
280800 -
280801 - http://www.eekim.com/ohs/lc/dialogmaps/ohs-lc-dm.png
280802 -
280803 -
280804 - .... that diagrams ideas in summary concept statements, beginning
280805 - with.....
280806 -
280807 - ..
280808 - What is a document? <---------- How Granular
280809 - should nodes be?
280810 -
280811 - ------------------- Author associates IDs
280812 - | with chunck of document
280813 - v e.g., purple numbers
280814 - How do you define a
280815 - document's data model
280816 - to promote component reuse?
280817 -
280818 - ^
280819 - |
280820 - ---------------- Use path addresses (e.g.
280821 - XPointer)
280822 -
280823 - ..
280824 - What is a "path <-------- Defies a path from one
280825 - address? node to another
280826 -
280827 -
280828 - ..
280829 - The page goes on in an excellent graphical display; changing formats
280830 - to text, the next section covers....
280831 -
280832 -
280833 - What are problems related to link integrity?
280834 -
280835 - Intended relationships may break if node or set of nodes are
280836 - moved around
280837 -
280838 - Content of nodes changes, but associated metadata is not
280839 - updated.
280840 -
280841 - Document is deleted
280842 -
280843 - ..
280844 -
280845 - What architectures can solve our problem?
280846 -
280847 - How might these take advantage of NODAL?
280848 -
280849 - What are the architectural issues?
280850 -
280851 - This section below is repetitious; would work to drop
280852 - "knowledge" since it takes up space and does not convey
280853 - anything.
280854 -
280855 - "Knowledge" was reported to be beyond the reach of this
280856 - group on 000615.
280857 - ..
280858 - The hard work Eugene is doing might pay off by
280859 - going ahead and explaining what folks mean by
280860 - "knowledge" as distinguished from "information"
280861 - insertion, extraction, etct.
280862 -
280863 - Knowledge insertion
280864 - Knowledge extraction
280865 - Knowledge navigation
280866 - Knowledge representation
280867 - Knowledge reduction
280868 - Knowledge elimination
280869 -
280870 -
280871 - ..
280872 -
280873 - How should we record Q&A sessions with Doug?
280874 -
280875 - Live IBIS map of discussion
280876 -
280877 - How to export maps
280878 - Will slow down meeting
280879 - More info on IBIS
280880 -
280917 -
280918 - ..
280919 -
280920 - What is OHS Launch Community?
280921 -
280922 - What software are members developing?
281048 - ..
281049 -
281050 - How will we be build our ontology?
281051 -
281052 - • Start by ontologizing Lee's NODAL documents
281053 -
281054 - This does not offer a lot of ideas on solving the
281055 - problem of complexity Jack Park cited on 000221.
281056 - ref SDS 10 7455
281057 -
281058 - Who is the ontologizer?
281059 -
281060 - What education and experience is needed for this
281061 - work?
281062 - ..
281063 - Who has done this previously other a
281064 - librarian or a secretary?
281065 -
281066 - When is the work performed, and with what tools?
281067 - What work product results?
281068 -
281069 - How is ontology applied, by whom, when and with what
281070 - tools?
281071 -
281072 - What happens when something doesn't fit the
281073 - ontology, which occurs about 100 times a day?
281074 -
281075 - • Release ontologies early and often
281076 -
281077 - This will be a mess!!!!
281078 -
281079 -
281080 - ..
281081 -
281082 - How should we build and maintain the DKR?
281083 -
281084 - Use purple numbers
281085 -
281086 - There does not seem to be a lot of options for
281087 - building the DKR. What about NODAL and Nexist?
281088 -
281089 - How do I add purple numbers to PDF or Word?
281090 -
281091 - Create HTML list of docs, and add purple numbers
281092 - there
281093 -
281094 - This solution is unclear, PDF is an inert
281095 - picture.
281096 -
281097 - Is it proposed to type the PDF file into Word
281098 - or NODAL, Nexist, then run Purple?
281099 - ..
281100 - Use Purple to create XML files, convert to
281101 - XSL/FO, convert to PDF
281102 -
281103 - Why use PDF/Word rather than HTML?
281104 -
281110 -
281111 -
281112 -
281113 -
2812 -
SUBJECTS
Dialog Mapping Takes Time
Work Role New Needed for Culture of Knowledge Co-evolve Education Alo
KM Dilemma Lot of Extra Time Needed for Dialog Mapping to Increase Sp
Time Saved SDS Adds Intelligence to Management Proactive Problem Hand
New Way Working Thinking SDS Paperless Office Virtual Office
Intelligence Added to Management is Fun and Effective
Not Enough Time to Read and Write Learn to Save Time Using SDS for Im
Dialog Mapping Organize Record Ontology Takes Effort Time Need Ontolo
7611 -
761101 - ..
761102 - New Work Role Ontologist Convert Information into Knowledge
761103 - KM Dilemma Improving the Work Takes More than 20 Minutes
761104 - Organizing Record Takes Time, New Profession - Ontologist
761105 -
761106 - Follow up ref SDS 61 4J4J, ref SDS 60 4J4J.
761107 -
761108 - Eugene confirmed it takes a lot of time to create the dialog map of
761109 - email, per example above. ref SDS 0 NX6N
761110 -
761111 - I congratulated Eugene on making the effort without any tools, methods
761112 - nor help.
761113 -
761114 - There is discussion of ontology in dialog map that simply says an
761115 - ontology should be developed from Lee Iverson's NODAL work.
761116 - ref SDS 0 XJ8F
761117 - ..
761118 - It is not clear why Doug's work and Eric Armstrong's work
761119 - are not used to help build a sufficiently expansive structure that
761120 - might be able to accomodate this effort.
761121 -
761122 - Eugene explained there is no codifying sytem reported earlier by Eric
761123 - on 010916, ref SDS 60 6O6I, for organizing the record, there is no
761124 - mention of an ontologist, also, mentioned by Eric on 010916,
761125 - ref SDS 60 4J4J, although Eugene would initially fill that role by
761126 - default, and no other evident method of organizing other than
761127 - outlining and flow diagraming, per above, ref SDS 0 NX6N,
761128 -
761129 - There is no summary nor links to anything but email, so this system is
761130 - in the early stages of improving the ability to find anything.
761131 -
761132 - Ontology is discussed only in relation to NODAL, and merely sets an
761133 - agenda to work on this at some time in the future. ref SDS 0 XJ8F
761134 - ..
761135 - Why would Doug's work and Eric's work on CDS be used for
761136 - the ontology?
761137 -
761138 - This system will have difficulty maintaining relevance.
761139 -
761140 -
761141 -
761142 -
761143 -
7612 -
SUBJECTS
Ontology Inspection Agents Engine Mine Email Archive
AI Ontology Semantically Rich Knowledge Bases Enable Intelligent Appl
Ontology Vocabulary for Mediators, Agents of AI Effort, 000221
Mediators, Stanford
Engine Ontology Inspection Agent, Eugene Kim, Eric Armstrong, 010916
9408 -
940801 - ..
940802 - Engine Mine Archive Produce Ontology Monitored by Ontologists
940803 - Ontology Inspection Agent Engine Automates Organizing Record
940804 -
940805 - Follow up ref SDS 61 8M6K, ref SDS 60 8M6K.
940806 -
940807 - Eugene did not mention work underway for ontology inspection agents,
940808 - cited by Eric Armstrong in his letter on 010916, ref SDS 60 8M6K, nor
940809 - is there an mention of this capability in OHS Launch Community
940810 - planning, reviewed above. ref SDS 0 XJ8F
940811 -
940812 -
940813 -
940814 -
940815 -
940816 -
9409 -
SUBJECTS
Willfully Blind, Fear and Denial
Overlook SDS Culture of Knowledge Eugene Kim Eric Armstrong Ignore SD
A20401 - ..
A20402 - Boggled Mind Blind to Solutions that Appear Beyond Reach
A20403 -
A20404 - Follow up ref SDS 61 I58K.
A20405 -
A20406 - Apologized for strident remarks in the letter, ref DIP 12 0001, sent
A20407 - on 010917. ref SDS 61 I58K, responding to a letter Eugene sent on
A20408 - progress using dialog mapping, ref DRP 15 0001, for organizational
A20409 - memory to support the OHS Launch Community, which was received earlier
A20410 - on 010917. ref SDS 61 9R6I
A20411 -
A20412 -
A20413 -
A20414 -
A20415 -
A20416 -
A205 -
SUBJECTS
SDS Supports Organizational Memory Should be Studied
SDS Proposal to Learn KM by Using SDS Supported
Vatant, Bernard Has Done Excellent Work Organizing Email Archive
Knowledge Integration Problem No Single Solution
Knowledge Not Well Enough Understood to Develop Knowledge Management
Topic Map OHS/DKR Eugene Will Submit Internet Address for Work by Ber
A909 - 0934
A910 -
A91001 - ..
A91002 - Bernard Vatant Developed Useful Topic Map for OHS/DKR Archive
A91003 - Study SDS for Organizational Memory
A91004 -
A91005 - Follow up ref SDS 61 H86F.
A91006 -
A91007 - Expressed appreciation for Eugene's generous remarks about SDS in his
A91008 - reply letter, ref DRP 17 0001 on 010917. ref SDS 61 PPUT
A91009 -
A91010 - Asked Eugene for a web address that shows the work cited in his letter
A91011 - on 010917 crediting Bernard Vatant's use of topic maps to organize the
A91012 - OHS/DKR project record. ref SDS 61 H86F
A91013 -
A91014 - Eugene advised he has misplaced the address, but will do some research
A91015 - and submit an email with a link to the location showing Bernard's work
A91016 - using topic maps for the OHS/DKR project.
A91017 -
A91018 -
A91019 -
A91020 -
A91021 -
A91022 -
A91023 -
A91024 -
A91025 -
A91026 -
Distribution. . . . See "CONTACTS"