CONTACTS 

SUBJECTS
Knowledge Different from Information
KM Different from IT
Theory of Knowledge Chronology Causation Experience
Chronologies Cause and Effect Based on Subject = Patterns Context Int
Chronology History Experience Causation Intelligence
Chronology Organizes Complexity Context Faster Better Cheaper
Chronology = Causation + Meaning Symbols Signs Semiotics = Communicat
Chronology Organize Information Intelligence Time
Define Knowledge Different from Information
Chronology Time Organizing Criteria for Knowledge, Gelernter, Jack Pa
Communicaiton Supports Design Rationale, Shipman, McCall
AI Design Rational from Design Communication, Shipman, McCall
Information Capture Continuous Stream Chronology, Johnson, Gary, 0012

3715 -
3715 -    ..
3716 - Summary/Objective
3717 -
371701 - Follow up ref SDS 52 RD9N
371702 -
371703 - Research in AI work for software design supports aspects of SDS,
371704 - particularly capturing communication as a continuous information
371705 - stream, ref SDS 0 AE6H, and organizing it according to multiple
371706 - subjects, ref SDS 0 GR3K, to reflect evolving context. Experience with
371707 - outlining yields insights on hierarchial organization. ref SDS 0 F36I
371708 - Organizing information is called "refractoring." ref SDS 0 I53M  A
371709 - dedicated "knowledge expert" is proposed for KM, which aligns with Com
371710 - Metrics. ref SDS 0 DW5I A new set of requirements/specs are offered,
371711 - that includes an "engine" which seems similar to work by Eric
371712 - Armstrong and and Jack Park earlier in the year. ref SDS 0 AK9I
371713 -
371714 -
371715 -
371716 -
371717 -
371718 -
371720 -  ..
3718 -
3719 -
3720 - Progress
372101 -  ..
372102 - Theory of Knowledge Proposed Distinguished from IT
372103 -
372104 - Follow up ref SDS 52 RD9N.
372105 -
372106 - Received ref DRT 1 0001 from Gary Johnson following up his letters to
372107 - the team on...
372109 -        ..
372110 -       001219, ref SDS 51 6A9N purpose of KM
372111 -       001220, ref SDS 52 BV3W competency and values
372112 -       001221, ref SDS 53 513O social problems solved by KM
372114 -  ..
372115 - The letter today, cites Gary's letter on 001220 referencing work of
372116 - Frank Shipman, ref SDS 52 813M, listing following.....
372117 -
372118 -    http://www.csdl.tamu.edu/~shipman/,
372119 -
372120 -    http://www.csdl.tamu.edu/~shipman/formality-paper/harmful.html .
372122 -     ..
372123 -    http://www.csdl.tamu.edu/~shipman/aiedam/aiedam.html
372124 -
372125 -        [On 011006 Shipman proposes incremental formalization to
372126 -        overcome resistance to organizational memory. ref SDS 74 F44L
372127 -
372129 -     ..
372130 -    Capture Continuous Information Stream Showing Chronology
372131 -
372132 -
372133 - Gary draws from research on Shipman's work that......
372134 -
372135 -
372136 -    ....we need ways to capture information as it arises, and connect
372137 -    it in various ways later. ref DRT 1 GT6L
372138 -
372139 -       [On 001224 Gary says attribution is important. ref SDS 54 6I7K
372141 -  ..
372142 - This understanding is not linked to anything, but seems to come from
372143 - Shipman's paper, ref OF 7 017Q .....
372144 -
372145 -                ..
372146 -             Integrating Different Perspectives on Design
372147 -             Rationale: Supporting the Emergence of....
372149 -  ..
372150 -
372151 -             Design Rationale from Design Communication
372152 -
372153 -
372154 - ....co-authored, per......
372155 -
372156 -             Frank M. Shipman III
372157 -             Department of Computer Science
372158 -             Texas A&M University
372159 -             College Station, TX 77843-3112
372160 -             E-mail: shipman@cs.tamu.edu
372162 -              ..
372163 -             Raymond J. McCall
372164 -             College of Environmental Design & Institute of
372165 -             Cognitive Science
372166 -             University of Colorado, Boulder
372167 -             Boulder, CO 80309
372168 -             E-mail: mccall@spot.colorado.edu
372169 - ..
372170 - The paper seems to have been published in......
372171 -
372172 -
372173 -       Artificial Intelligence in Engineering Design, Analysis, and
372174 -       Manufacturing (AIEDAM), 11, 2 (April, 1997), pp. 141-154.
372175 -
372176 -
372177 - .....according to Shipman's biography on the Internet at......
372178 -
372180 -                 ..
372181 -                http://www.csdl.tamu.edu/~shipman/
372182 -
372184 -  ..
372185 - In particular, Shipman and McCall state......
372186 -
372187 -    1.2 The Communication Perspective
372188 -    ..
372189 -    For some people, DR means capturing and retrieving naturally
372190 -    occurring communication--e.g., design discourse--among members of a
372191 -    project team. The goal here is recording thought that has occurred
372192 -    rather than shaping the thought that occurs.  The recording of
372193 -    design communication is not meant to have any effect on the design
372194 -    process.  It is merely meant as a way of retrospectively tracking
372195 -    down various information that might have been the subject of
372196 -    communications among participants in the design process.
372197 -    ref OF 7 017Q
372198 -
372200 -  ..
372201 - The authors appear to clarify intent is to capture a full recording of
372202 - communication, as with a tape recorder, video film, etc.....
372203 -
372204 -    Recorded communication therefore typically includes all sorts of
372205 -    information irrelevant to the argumentation or documentation
372206 -    perspectives--e.g., discussions about scheduling meetings or even
372207 -    about the weather. ref OF 7 2Z5I
372208 -    ..
372209 -    Recorded communication also tends to lack the discipline and
372210 -    structure of the other two types of DR. Both argumentation and
372211 -    documentation attempt to impose some sort of order on the record of
372212 -    things discussed. ref OF 7 016L
372213 -
372214 -        The view that information is "irrelevant" often proves to have
372215 -        been inaccurate, under evolving context.  Typically, it is
372216 -        better to capture more, rather than less.
372218 -         ..
372219 -        On the other hand, a pure tape recording is generally
372220 -        worthless, except as a guide to prepare analysis supported by
372221 -        the original record, as reported on
372222 -
372223 -           880907............... ref SDS 1 MM7G
372224 -           950223............... ref SDS 4 8492
372225 -           950320............... ref SDS 5 0788
372226 -
372228 -  ..
372229 - Intelligence Requires Organization, Analysis, Summary, Feedback
372230 -
372231 - Gary's conclusion from Shipman and McCall is a step toward POIMS
372232 - design supported by SDS method for capturing a continuous information
372233 - stream to preserve chronology, i.e., sequence, ref OF 1 079L, and
372234 - adding explicit organization to create useful "chunks" (from the term
372235 - proposed by George Miller, reviewed on 990303, ref SDS 8 2838), that
372236 - compliment, verify and preserve implicit organization provided by
372237 - natual intelligence, ref OF 1 0367, so that chronologies of cause and
372238 - effect can be assembled when needed based on contextual subject
372239 - structures. ref OF 1 1110
372241 -  ..
372242 - Shipman and McCall, as well, recognize organization (they call it
372243 - "indexing") is needed to make chronologies useful. ref OF 7 F86K
372244 - ..
372245 - Structure is cited as critical, ref OF 7 XF5J, and it must be
372246 - flexible to meet variable demands based on evolving context of daily
372247 - work and conditions. ref OF 7 YD4L  SDS supports this objective with
372248 - flexible outlining, and summary connected to detail, as key aspects of
372249 - "intelligence" explained in POIMS. ref OF 1 0367
372251 -  ..
372252 - An AI systemis proposed that integrates text with other forms of
372253 - information, e.g., pictures, audio, film, etc. ref OF 7 MF3K
372254 -
372255 -      One challenge the authors do not address is the time required to
372256 -      maintain the record.  As a result, primary attention must be
372257 -      given to the primary goal of understanding what was done, why and
372258 -      correlations and implications, which mainly requires language and
372259 -      math that provide a coherent "story," per Campbell, reviewed on
372260 -      900303. ref SDS 2 3016  More recently, on 000307 the need for a
372261 -      "story" to synthesize information into a useful form for decision
372262 -      support, was cited. ref SDS 21 0783
372263 -
372265 -       ..
372266 -      Timely Information in Context is Useful Knowledge, Intelligence
372267 -
372268 -
372269 - The authors say near the end of the paper.......
372270 -
372271 -      To make this information useful during design, both critics in
372272 -      PHIDIAS and agents in HOS are meant to provide designers with
372273 -      information when they need it but do not know it. By providing
372274 -      information to designers in the context of design, these
372275 -      mechanisms make the information serve the design, and ultimately
372276 -      the original goals of the three perspectives discussed.
372277 -      ref OF 7 IP6H
372278 -
372279 -         Why not make timely "intelligence" available to everyone?  Why
372280 -         is "intelligence" focused solely on designing stuff?
372281 -         ..
372282 -         Let's empower everyone, e.g., doctors, lawyers,
372283 -         gardners, plumbers, managers, salesmen, et al., to get
372284 -         intelligence when needed to mow the lawn, read a book, go to
372285 -         the doctor, fix the car, prepare dinner, attend a meeting,
372286 -         make a call, install a turbine generator in a hydro electric
372287 -         dam -- don't we need it for everything?
372288 -
372290 -  ..
372291 - Two systems are identified as prototypes developing the capabilities
372292 - set out in the paper. ref OF 7 U48L
372293 -
372295 -  ..
372296 - Gary continues....
372297 -
372298 -    I like the information annealing concept. Annealing in materials
372299 -    refers to the process of heating a material until it is possible
372300 -    for molecules in the material to move slightly without distorting
372301 -    the material, and then allowing the material to cool slowly. This
372302 -    process removes local strains from the system as the molecules
372303 -    adjust their positions. ref DRT 1 YW7O
372304 -
372305 -
372306 -
372307 -
372308 -
372309 -
3724 -

SUBJECTS
Communication Manager Support Knowledge Worker
Knowledge Worker Communication Manager
Communication Manager Saves Time So Managers Have Time to Think
Com Manager Role Needed for KM, Doug Engelbart
Com Manager Knowledge Worker Organizes Links Aligns Correlations Impl
Communication Manager Aligns Team Metrics Proactive
Communication Manager Buffers Shock of Management Details

4909 -
491001 -     ..
491002 -    Communication Manager Supports Daily Intelligence
491003 -
491004 -
491005 - Gary says....
491006 -
491007 -    Neil Larson uses the term "information annealing" to refer to a
491008 -    similar process in group hypertext systems, and believes that at
491009 -    least some of it must be done by a....
491010 -
491011 -                        knowledge expert
491012 -
491013 -    ....in order to be effective. ref DRT 1 PPTT
491015 -  ..
491016 - Seems to support POIMS, ref OF 1 5820 and ref OF 1 HO4H.
491017 - ..
491018 - NWO..., also, calls for a dedicated role, ref OF 2 6369, to be a
491019 - pilot that uses specialized "intelligence" tools, like an accountant
491020 - uses a spreadsheet program.
491022 -  ..
491023 - Doug Engelbart calls for this support.....
491024 -
491025 -    1972 paper calls for "special expertise," reviewed on 000327.
491026 -    ref SDS 22 5256
491027 -
491028 -    OHS Launch Plan, reviewed on 001025. ref SDS 42 8094
491029 -
491030 -
491031 -
491032 -
491033 -
491034 -
4911 -

SUBJECTS
Subject Indexing
Formality Considered Harmful, Frank Shipman, Catherine Marshall
Organic Structure Power of Microcosm Control Lower Levels Improve Pro
Ontology Organic Subject Structure WBS Methodology
Organize Complexity Ontology Digging Ditch
Organic Subject Structure Assemble Record on Particular Issues
Balance Organic Structure with Flexibility
Rigid Structure Reduces Productivity, e.g., IBIS
Structure Rigid Hampers Productivity KM Dilemma, e.g., IBIS
IBIS Rigid Rules Prevent Effective KM, Gary Johnson
Flexible Structure Supports KM, Gary Johnson, SDS Provides Flexible S
IBIS History Origins, Rittle, 001222
Outline Hierarchial Structure Conveys Meaning Context
Refractoring Organize Chronology Hierarchial Subjects, 001222, Gary J
Subjects Finding Information Requires Effective Organic Structure

8117 -
811801 -  ..
811802 - Formal Information Structure Resisted - Need Flexibility
811803 -
811804 - Follow up ref SDS 52 RD9N.
811805 -
811806 - Gary continues arguments presented on 001220, saying today.....
811807 -
811808 -     The short form of the arguments presented in the references is
811809 -     that we resist formalisms that categorize things before we are
811810 -     comfortable with the categories that are available:, ref DRT 1
811811 -     009I
811813 -            ..
811814 -        •  We leave files out where we can get at them until we have
811815 -           some place to put them or things get too messy. This is true
811816 -           of paper, disk directories, and email systems. It appears to
811817 -           be true in all information systems maintained by people.
811819 -            ..
811820 -        •  When we evolve categories, there is concern about getting it
811821 -           wrong, so we delay.
811822 -
811824 -      ..
811825 -     IBIS Formal Argumentation Structure - History of IBIS
811826 -     Structure, Appearance Impart Meaning of Text
811827 -
811828 -     I found it fascinating that people hesitate to follow formalisms
811829 -     such as IBIS even when study of their actual behavior indicates
811830 -     that the formalism is just what they do. I think this is related
811831 -     to the similar problem of word processing where we have to look at
811832 -     issues of structure and appearance before we are really certain of
811833 -     the content. ref DRT 1 005J
811834 -
811835 -         IBIS is discussed in Shipman's paper. ref OF 7 006K
811837 -          ..
811838 -         This approach was originated by Rittel [Rittel 1972], and the
811839 -         best-known examples of it are based on his Issue-Based
811840 -         Information System (IBIS) framework for argumentation [Kunz,
811841 -         Rittel 1970]. ref OF 7 10SF
811842 -
811843 -
811845 -      ..
811846 -     Subjects Organize Information
811847 -     Organization Required for Effective Intelligence - Refractoring
811848 -
811849 -
811850 - Gary calls for ability to organize information.....
811851 -
811852 -     Refactoring is the term used in Object Oriented design to refer to
811853 -     the necessity for reorganizing class and other code structures as
811854 -     a project progresses and better abstractions are discovered.
811855 -     ref DRT 1 GL6O
811856 -
811857 -          [On 001222 Gary uses "refactoring" to explain adding
811858 -          alignment to continually refine understanding of
811859 -          communication beyond software engineering. ref SDS 75 YR9K
811860 -
811861 -     ....it is necessary to be able to refactor information at any
811862 -     stage. It would be nice if the base material were still available
811863 -     also as a check on the refactoring, but the refactoring is
811864 -     essential.  Human knowledge, particularly in the hard sciences is
811865 -     subject to this sort of refactoring in a largely uncontrolled way.
811866 -     We no longer use the alchemists theory of the universe as part of
811867 -     our current knowledge base - it has been refactored out. We do,
811868 -     however, have some degree of access to the historical documents
811869 -     that reflect that refactoring process. ref DRT 1 Z94J
811870 -
811871 -          [On 020618 Gary discussed a refractoring browser used for
811872 -          source code editing, in the context of managing the
811873 -          complexity of organic structure, and consequent potential for
811874 -          consultants and experts to make a living by creating
811875 -          standardized structures for particular fields. ref SDS 77
811876 -          PQYX
811878 -          ..
811879 -         On 000709 Bill DeHart at PG&E reported SDS works better than
811880 -         wordprocessing for organizing information. ref SDS 35 1029
811881 -
811882 -
811883 -
811885 -      ..
811886 -     Cross-Referenced Subject Indexes Need Efficient Editing
811887 -     Hierarchial Structure Generated from Outlining
811888 -     Outlining Reflects Organic Subject Structure Methods
811889 -
811890 -
811891 - Gary says.....
811892 -
811893 -     Hierarchical organization is generally superior to linear
811894 -     presentation. The topic context provides all sorts of support for
811895 -     things that don't have to be said. The extensive quoting that we
811896 -     do in emails is indicative of the lack of context that we have in
811897 -     an essentially linear system (threads are linear internally).
811898 -     ref DRT 1 014M
811899 -
811900 -     ...hierarchy implicitly assumes information has exactly one place
811901 -     to go.  It doesn't take long working with this assumption before
811902 -     its invalidity is apparent. ref DRT 1 YE5O
811904 -      ..
811905 -     The first response is the ability of a topic to exist in multiple
811906 -     places in the hierarchy and still be a single topic - edit it
811907 -     anywhere and it changes everywhere. ref DRT 1 016P
811908 -
811909 -     ....humans organize information using multiple hierarchies, at
811910 -     least. The hierarchy used depends on the context of the
811911 -     information and the attributes that are considered relevant in
811912 -     that context. This leads to the observation that hierarchy needs
811913 -     to be separate from the content - it should be possible to supply
811914 -     as many hierarchies, indices, or other similar organizing schemes
811915 -     as desired to the content without forcing assumption on the
811916 -     content. This is recursive in that hierarchies become content
811917 -     which can in turn be referenced and reorganized. ref DRT 1 NR6O
811918 -
811919 -         This seems headed toward a notion of combining hierarchy
811920 -         with linear organization supported by SDS.
811922 -          ..
811923 -         Gary describes key aspects of SDS; would be helpful to edit a
811924 -         "subject" once, and update cross-references; a restraint is
811925 -         that subjects can be similar but not really the same.  This
811926 -         goes to granularity, which POIMS explains is actually fluid in
811927 -         the extreme, so it is a very complex issue. ref OF 1 0367  On
811928 -         000221 Jack Park described "ontology" as a pandora's box of
811929 -         complexity.  How might exactness established?  Jack's ontology
811930 -         "engine" proposed on 000623, ref SDS 34 2915, may help
811931 -         accomplish this somehow????
811933 -  ..
811934 - Gary explains practices for effective outlining, which have aspects of
811935 - managing SDS organic subject structure, and summary methods....
811936 -
811937 -     I used MaxThink, an outline based information tool for DOS, for
811938 -     years and use an outliner today. With MaxThink I found the
811939 -     following to be extremely useful:, ref DRT 1 00EK
811941 -             ..
811942 -         •  Write down a series of statements just as they came to
811943 -            mind. Use just enough explanation to remind me later of
811944 -            what I had in mind. ref DRT 1 NM5H
811946 -             ..
811947 -         •  When I ran out of things to put on the list, move things
811948 -            around to get some similar items together. ref DRT 1 WM5K
811950 -             ..
811951 -         •  When I could identify a few topics, add them at the top of
811952 -            the list and then do a "bin sort" which allowed me to move
811953 -            all the topics that were children of the new topics under
811954 -            the new topics. ref DRT 1 7N5N
811956 -             ..
811957 -         •  Iterate on this until relatively little motion occurs.
811959 -             ..
811960 -         •  Pick a topic and repeat.
811962 -             ..
811963 -         •  If a couple of topics look like they aren't working well,
811964 -            flatten their children to the next level up and continue
811965 -            the process. ref DRT 1 EN6L
811967 -      ..
811968 -     Using this approach I could generate a hierarchical document that
811969 -     was very coherent, and do it very quickly.  This applies
811970 -     formalisms largely after the fact.  Once there was a framework,
811971 -     some things had logical places to go, and I applied the formalisms
811972 -     to some new content as the content was generated. ref DRT 1 00GQ
811973 -
811974 -         Hierarchial structure is a key aspect of "intelligence" that
811975 -         develops useful organization which conveys meaning through
811976 -         context, and facilitates retrieval in context.
811978 -          ..
811979 -         On 910810 Morris described SDS as integrating hierarchial and
811980 -         relational design. ref SDS 3 7793
811982 -          ..
811983 -         SDS subject management and record organization is a little bit
811984 -         like this, and is applied for everything.  SDS tools make the
811985 -         work fast and easy to accomplish, but the amount of structure
811986 -         that is possible, and that is needed on to adequately segment
811987 -         the record into reasonable sized chunks of information for
811988 -         assembling chronologies, makes it a major task, rather like
811989 -         tending a garden of knowledge.
811991 -          ..
811992 -         The challenge is doing it quickly and, also, coherently, which
811993 -         Gary says he can accomplish.
811994 -
811995 -
811996 -
8120 -

SUBJECTS
Wordprocessing Does Not Support Outline Hierarchial Structure
Wordprocessing Context Time Chronology Organizes Complexity Context F
Wordprocessing Less Useful Than Text for Executives
Organize Information Time Chronology Experience Causation Understandi
Outline Hierarchial Structure Organizes Information, Gary Johnson

8507 -
850801 -      ..
850802 -     Wordprocessing Does Not Support Structure
850803 -
850804 -     Follow up ref SDS 46 0001, ref SDS 7 2156.
850805 -
850806 -     Once I moved the information into a word processor to get the nice
850807 -     formatting, I was dead.  There was no good way to manipulate the
850808 -     content again in the word processor.  If the organization go too
850809 -     messy I would export the word processing file back into MaxThink
850810 -     and work on the organization.  This of course lost all the
850811 -     formatting, so that had to be done all over when I brought it back
850812 -     into the word processor. ref DRT 1 BK3J
850813 -
850814 -         Lends support to POIMS premise that wordprocessing is good for
850815 -         improving appearance of information, but does not support
850816 -         adding "intelligence" that helps people think, remember and
850817 -         communicate. ref OF 1 0959  On 980405 Morris seemed to support
850818 -         this understanding. ref SDS 7 2156  More recently on 001122
850819 -         Eric Armstrong reported difficulty developing KM using a
850820 -         wordprocessing platform. ref SDS 46 0001
850821 -
850822 -            [On 020531 Mike Poremba creating Java outline program notes
850823 -            SDS optimized for efficient usability of program functions,
850824 -            ref SDS 76 5M3G; dates make sense of complex information so
850825 -            links are contextually comprehensible, ref SDS 76 OP7M, SDS
850826 -            support for timely analysis to aid human thinking is hard
850827 -            to achieve; DOS enables working at the speed of human
850828 -            thought. ref SDS 76 5W9J
850830 -             ..
850831 -            [On 021206 Mike Poremba demonstrates Java outline program
850832 -            with review of SDS. ref SDS 78 TGTU
850833 -
850834 -               http://www.dynamiclist.com/?node=4a2e5377-12fd-4982-96f0-d9e97c03a6c4
850835 -
850836 -
850837 -
850838 -
8509 -

SUBJECTS
Spagetti Code Software Engineering Methods
Structured Code Software Engineering Methods
Spagetti Code Software Engineering Methods
Structured Code Software Engineering Methods

9706 -
970701 -      ..
970702 -     Software Engineering Evolved Variety of Methods
970703 -
970704 -
970705 - Gary explains efforts in software engineerig to improve design
970706 - methodologies.....
970707 -
970708 -     •  Spaghetti code -
970709 -
970710 -        we can link anything to anything any time, access any
970711 -        information we want and go anywhere we like. We quickly
970712 -        discovered that humans cannot function effectively at that
970713 -        level of generality as the size of the information increases.
970714 -        ref DRT 1 6V9N
970715 -
970716 -     •  <IN73 Structured code -
970717 -
970718 -        every construct has a single entrance and a single exit. It is
970719 -        possible to construct any program with sequence, alternation,
970720 -        and repetition. Powerful. Now we have some degree of
970721 -        discipline. Code is easier to read, easier to write, and
970722 -        (somewhat) easier to get right. ref DRT 1 NV4I
970723 -
970724 -     •  Structured analysis -
970725 -
970726 -        any problem can be decomposed into a hierarchy of functions.
970727 -        This helped too, but ran into problems. ref DRT 1 WV4O
970728 -
970729 -     •  Data Structured Development -
970730 -
970731 -        problems are properly characterized by the nature and structure
970732 -        of the data that represents them. For problems on which this
970733 -        worked, it worked spectacularly. ref DRT 1 EW5H
970734 -
970735 -     •  <IN62 Object Oriented development -
970736 -
970737 -        both data and behavior must be considered when representing
970738 -        objects. Objects belong to classes, which describe the
970739 -        (hierarchical) set of data and behaviors that the object
970740 -        possesses. ref DRT 1 LW5L
970742 -         ..
970743 -        a. There is disagreement as to whether there can be multiple
970744 -           hierarchies or only one. ref DRT 1 5X6F
970746 -            ..
970747 -        b. Class membership is generally fixed. There are some systems
970748 -           and some techniques to allow an object to change its class
970749 -           dynamically. ref DRT 1 5X6I
970751 -            ..
970752 -        c. The set of behaviors and data structure that represent an
970753 -           object is fixed. ref DRT 1 HX6L
970755 -         ..
970756 -        d. <INWY Some say that the data and behavior is inadequate,
970757 -           that we have to understand and enforce the logical contract
970758 -           that represents the invariant promise of a functions
970759 -           behavior. ref DRT 1 RX6O
970760 -
970761 -     •  Frame based systems -
970762 -
970763 -        every object is unique although we can organize them into class
970764 -        hierarchies for description. Such systems allow the dynamic
970765 -        addition of data and/or behaviors to objects and sometimes
970766 -        classes. We are now at a level of representation that has been
970767 -        proposed for general knowledge representation. ref DRT 1 IY3I
970768 -
970769 -
970770 -
970771 -
9708 -

SUBJECTS
OHS/DKR Specs Requirements from Refractoring Software Engineering Met
OHS Architecture Eric Armstrong Creating Code for OHS to be Released
OHS Architecture, Gary Johnson, 001222
OHS Requirements Proposed by Gary Johnson
KM Design Requirements, Gary Johnson, 001222
Engine Map Topics Complexity Ontology Pandaora's Box of Complexity On

A508 -
A50901 -  ..
A50902 - OHS/DKR KM Requirements Need Alignment with OHS Project History
A50903 -
A50904 - Gary proposes a set of requirements, or a process of developing
A50905 - requirements and specs, ref DRT 1 02GU, based on (he calls it
A50906 - "refractoring") practices of software engineering, per above,
A50907 - ref SDS 0 N69M, that evolved stronger forms of "knowledge
A50908 - representation, for an OHS/DKR, or generic KM system, which seems
A50909 - similar to those proposed by Eric Armstrong, reviewed in depth on
A50910 - 000505. ref SDS 30 0001
A50912 -  ..
A50913 - Gary proposes an "engine," which is anticipated to be difficult, but
A50914 - achievable, if scope is limited. ref DRT 1 02H1,
A50915 -
A50916 -     Issues that seem to arise from Gary's work today......
A50917 -         ..
A50918 -     1.  Need definition of "knowledge" that is proposed to be
A50919 -         "represented"?
A50921 -          ..
A50922 -         How does "knowledge representation" in Gary's proposal relate
A50923 -         to Paul Fernhout's analysis on 000405? ref SDS 24 B8R4
A50925 -          ..
A50926 -         Gary's explanation about capturing informtion chronologically
A50927 -         is a good start. ref SDS 0 AE6H
A50929 -          ..
A50930 -     2.  How do Gary's specs and planning relate to.....
A50931 -
A50932 -         Eric Armstrongs' submission on 000505, ref SDS 30 0001, and
A50933 -         later on 000605? ref SDS 31 0001
A50935 -          ..
A50936 -         Engine proposed by Jack Park on 000623. ref SDS 34 2915
A50937 -         ..
A50938 -         Engine for links and subjects proposed by Jack on
A50939 -         001130. ref SDS 48 MN3W
A50941 -          ..
A50942 -         Paul Fernhout's analysis of "engine" on 001025 based on Jack's
A50943 -         submissions. ref SDS 42 LR6N
A50945 -          ..
A50946 -     3.  How would Gary's system improve knowledge work for.....
A50947 -
A50948 -         Software engineering
A50949 -         Digging a ditch
A50950 -         Visiting the doctor
A50951 -         Reading a book
A50952 -         Attending a meeting
A50953 -         Flying to Mars
A50954 -
A50955 -
A50956 -
A50957 -
A50958 -
A50959 -
A50960 -
A510 -