CONTACTS 
0201 - Armstrong Consulting                 650 845 1782
020101 - Mr. Eric Armstrong
020102 - eric.armstrong@eng.sun.com

SUBJECTS
Difficult KM Hard to Design, Not Understood
Core Capability KM Not Understood, Eric Armstrong
KM Not Understood Secret of SDS
XML OHS Design Ken Holeman New Contributor
Holeman, Ken, Meeting on Using XML for KM Design, Eric Submits Notes
OHS/DKR Meeting at Doug Engelbart's House with Ken Holman on XML
XML -> OHS Browser, Grant Bowman, 000812
XML Data Format
XML Translate from Text, HTML, Multiple Views, 000824

1411 -    ..
1412 - Summary/Objective
1413 -
141301 - Follow up ref SDS 47 0000, ref SDS 46 0000.
141302 -
141303 - Eric reports that Ken Holman has expertise with system design,
141304 - ref SDS 0 D74G, XML, ref SDS 0 M3RW, and topic maps. ref SDS 0 3Q5M
141305 - Participation in professional organizations, and strong communication
141306 - skills show that Ken can support open source collaboration. He can
141307 - help the team define an interchange standard obtain recognition.
141308 - ref SDS 0 389M   Ken wants to help advance Doug's objectives for OHS
141309 - and DKR.  No express reference is made to the Launch Plan Doug
141310 - submitted on 001017, nor to any other specific objective set in
141311 - requirements prepared over the past 10 months.  Ken's explanation of
141312 - topic maps to define OHS interchange mechanisms clarified issues. Eric
141313 - wants more information on this topic. ref SDS 0 0168
141314 -
141315 -      [On 001114 Ken's ideas reviewed at follow up meeting. ref SDS 48
141316 -      5Y6G
141317 -
141318 -      [On 001124 Ken submits clarifications on limitations of XML for
141319 -      OHS/DKR development. ref SDS 49 0001
141320 -
141321 -
141322 -
141323 -
141324 -  ..
1414 -
1415 -
1416 - Progress
1417 -
141701 -  ..
141702 - Ken Holman Introduced at Team Meeting on 001111
141703 -
141704 - Received ref DRT 1 0001 from Eric explaining understandings from a
141705 - meeting with Ken Holman at Doug's house on 001111.  Ken Holman very
141706 - much wants to make whatever contribution he can, which pretty much
141707 - makes him "one of the team".
141708 -
141709 -      Has Ken submitted a resume to Mark, per planning on 001017?
141710 -      ref SDS 38 01EY
141711 -
141712 - Eric does not privide an attendance list.  He does not say that Mark
141713 - Mitchell, assigned as OHS project manager on 001017, ref SDS 38 O25H,
141714 - attended the meeting.  A copy of Eric's letter went to SourceForge,
141715 - which is Mark's company. ref DRT 1 00W2
141716 - ..
141717 - Ken is very knowledgable about XML and related disciplines. And
141718 - he is, or has been, very active at OASIS (Organization for the
141719 - Advancement of Structured Information Standards). He is looking
141720 - forward to helping us define an interchange standard, and shepard it
141721 - through the various committees, and so on. ref DRT 1 KU5N
141722 -
141723 -      [On 001124 Ken submits clarifications on limitations of XML for
141724 -      OHS/DKR development. ref SDS 49 0001
141725 - ..
141726 - Eric reports that Ken has a remarkable flair for design. He
141727 - picked up a rough sense of what we were about in fairly short order,
141728 - and began making insightful observations based on his past design
141729 - experience. ref DRT 1 2V6I
141730 -
141731 -      On 001017 Eugene Kim said that OHS architecture is not developed,
141732 -      and this would be done by the new team. ref SDS 38 TJ3G
141733 -
141734 -      On 001025 Doug submitted an OHS Launch Plan, and requested that
141735 -      communications link to original sources. ref SDS 42 00VU
141736 -
141737 -      There are no links showing correlations nor alignment in Eric's
141738 -      report with any project objectives, history, specs or the Launch
141739 -      Plan.
141740 -
141741 -
141742 -
141743 -
141744 -
141745 -
141746 -
141747 -
1418 -
1419 -

SUBJECTS
XML -> OHS Browser, Grant Bowman, 000812
XML Data Format
XML Translate from Text, HTML, Multiple Views, 000824
XML - Extended Markup Language

2307 -
230701 -  ..
230702 - XML Basics Cover Methods for Presenting and Managing Documents
230703 -
230704 - Eric explains Ken's discussion on XML basics. ref DRT 1 XF7F
230705 -
230706 - He does not expressly correlate XML basics to the context of knowledge
230707 - management, to the requirements Eric prepared, to the new system he is
230708 - developing, nor to the Launch Plan Doug submitted on 001025.
230709 -
230710 -      [On 001114 Ken's ideas reviewed at follow up meeting. ref SDS 48
230711 -      5Y6G
230712 -
230713 - Eric reports that SCHEMATRON, ref DRT 1 0067, totally solves the XML
230714 - limitation described in his paper on XML Editor Design. ref DRT 1 GH4L
230715 - There is not description of the problem, there is no link to the
230716 - problem in the paper, nor to the paper, nor is there an explanation of
230717 - where the paper is located, and how the solution to the XML limitation
230718 - advances KM.
230719 -
230720 -      [On 001124 Ken submits clarifications on limitations of XML for
230721 -      OHS/DKR development. ref SDS 49 0001
230722 - ..
230723 - XSLT is a translation mechanism that can generate XML, which can
230724 - then be parsed. ref DRT 1 00U3   This may support Doug's objective in
230725 - the Launch Plan, reviewed on 001025, to translate documents.
230726 - ref SDS 42 T3D8
230727 -
230728 - Design concepts were discussed in relation to document style and
230729 - presentation issues. ref DRT 1 007X
230730 -
230731 -
230732 -
230733 -  ..
230734 - Determine OHS Services Required, Before Desiging System
230735 -
230736 - Ken recommended basing the design on functions and services,
230737 - rather than attempting to define a DTD for a "normal form."
230738 - ref DRT 1 0126 Eric supports this design method. ref DRT 1 0142
230739 -
230740 - Addressability is an example of a service, however, Eric does not
230741 - provide a reference nor a link to the Launch Plan on 001025.
230742 - ref SDS 42 D3W8
230743 -
230744 -      [On 001124 Ken submits letter confirming the recommendation to
230745 -      identify services for OHS/DKR. ref SDS 49 AW6L
230746 -
230747 -
230748 -
230749 -
230750 -
2308 -

SUBJECTS
Topic Maps Supported by Ken Holman, Jack Park, Eric Does Not Understa
Topic Map Graphical Map Organize Navigate Record
Search Engine Apply Topic Map Assemble Record Find Information
Pandaora's Box of Complexity Ontology, Jack Park
Topic Maps Graphical Maps Organize Record for Reporting
Lens Filter Graphical Maps Organize Record for Reporting

4709 -
470901 -  ..
470902 - Topic Maps Organize the Record According to Context
470903 -
470904 - Ken talked about topic maps, and expressed confidence in this method.
470905 - He mentioned Jack Park's advocacy several times in this context.  Eric
470906 - does not "get" Topic Maps. ref DRT 1 0163
470907 -
470908 -      Topic Maps sound like lens Mary Keeler and Jack Park presented in
470909 -      conjunction with ontology during the meeting at SRI on 000517.
470910 -      ref SDS 18 2812
470911 -
470912 -          How does this relate to graphical lens technology Doug asked
470913 -          about on 001008, ref SDS 33 5RW6, and Sheldon's report on
470914 -          001010? ref SDS 34 5RW6
470915 -      ..
470916 -      On 001008 Eric evaluated graphical representation, seems to
470917 -      indicate this method not practical for large scale Knowledge
470918 -      Management. ref SDS 33 N38W
470919 -
470920 -            [On 010912 Eric confirmed graphical technology not
470921 -            effective for KM. ref SDS 50 0001
470922 -
470923 -            [On 010912 Eric submits analysis on why graphical
470924 -            representation is not practical for daily Knowledge
470925 -            Mangaement. ref SDS 51 0001
470926 -
470927 -      Topic Maps were initially discussed on 000125 in connection with
470928 -      information structures and organization to provide context and
470929 -      assemble reports, using a search engine system. ref SDS 7 9246
470930 -      ..
470931 -      Recently, on 001019 Gil Regev explained context is very
470932 -      useful. ref SDS 40 TF5H  On 001025 Jack and Paul Fernhout
470933 -      discussed context as a useful feature of knowledge management.
470934 -      ref SDS 42 I58G
470935 -
470936 -      Earlier, Jack cited Topic Maps on 000403, ref SDS 12 1144, which
470937 -      is related to ontology and plans to create an evolutionary
470938 -      epistomology created by a processor "enginer" Jack is developing,
470939 -      per his letter on 000623. ref SDS 24 2915   On 001025 Paul
470940 -      Fernhout discusses design problems developing this capability,
470941 -      ref SDS 42 LR6N, which Jack cited in a letter to the team on
470942 -      000221, likening the task to opening Pandora's Box. ref SDS 8
470943 -      7455
470944 -
470945 - ..
470946 - Eric reports that Ken's comments indicated...
470947 -
470948 -    •  Topic maps provide a way of defining the semantic content of a
470949 -       structure or, perhaps more accurately, it is a way of specifying
470950 -       the syntax that is used to represent different semantic
470951 -       constructs. (I believe that is accurate, although I didn't quite
470952 -       get how it works. ref DRT 1 PH9K  More info...
470953 -
470954 -             http://www.topicmaps.org
470955 -
470956 -          Opening this address showed a message saying the folks are
470957 -          still "moving in" shortly, so there was nothing the provided
470958 -          more information.
470959 -
470960 -          Do Topic Maps relate to multiple views in the Launch Plan
470961 -          submitted on 001025? ref SDS 42 D6H8
470962 -
470963 -          Similarly, how does it support DKR, also, reviewed on 000125.
470964 -          ref SDS 42 C9WP
470965 -
470966 -          Any correlation with Eric's work on catagories in the record
470967 -          on 000601? ref SDS 19 5933
470968 -
470969 -    •  <0168 Ken suspects we want to use topic maps to define the OHS
470970 -       interchange mechansims. (Again, I don't see how that works,
470971 -       exactly, but I suspect that he and Jack will be able to arrive
470972 -       at a meeting of the minds.), ref DRT 1 0168
470973 -
470974 -    •  My one little "aha" on the subject is that if XSLT + a
470975 -       stylesheet can be used as the input to an application, then if
470976 -       the input is defined using a topic map, then anyone can use any
470977 -       syntax they want to encode the data -- the syntax will be
470978 -       transformed by XSLT for use by the application anyway, and that
470979 -       translation will be governed by the topic map. (I think that is
470980 -       somewhere within a Silicon-valley commute of being correct,
470981 -       but...), ref DRT 1 WA5F
470982 -
470983 -
470984 -
470985 -
470986 -
470987 -
470988 -
470989 -