Click here to comment!
1...Need explanation of how to correct defects in email that
2...When will design be available for review? What criteria
3...What progress has occurred on mock ups the past 40 days?.
4...Need list of tasks and WBS scope to aid folks in beginning
CONTACTS
0201 - Eugene Eric Kim O-00000756 0101
020101 - Mr. Eugene Eric Kim O-00000756 0101
SUBJECTS
Quiet No Activity on DKR Project, Eric Project
Quiet Slow Progress on DKR Project
Industry Doesn't Know How to Design KM
Progress Slow DKR Project People Don't Know What to Do
Dilemma Need Different from Market Demand
KM Secret of SDS, 000425
Progress OHS Development, 000928
Contributors Begin Production Work on OHS
Objective Settled, Eugene Kim
Client Mockups, Prototypes, Sheldon, Paul, Eugene Kim
Design Settled, Eugene Kim
Augment to HTML Script Supports Doug Providing Augment Design History
Objective of Project Not Commonly Understood, Eugene Kim
Objective will be Disseminated Later, Eugene Kim
Production Can be Started by Contributors Eugene Kim
Mockups, Prototypes, Sheldon, Paul, Eugene Kim
Mock Up Screens Being Developed by Sheldon
3119 -
3119 - ..
3120 - Summary/Objective
3121 -
312101 - Follow up ref SDS 81 0000, ref SDS 79 0000.
312102 -
312103 - Received ref DRT 1 0001 from Eugene Kim responding to a letter from
312104 - Grant Bowman, a contributor on the extended DKR team, asking...
312105 -
312106 - What's the scoop elsewhere? Do we have tons of funding yet
312107 - through SRI?
312108 -
312109 - Grant's letter was a response to the letter, ref DRP 8 0001 from Eric
312110 - Armstrong yesterday, ref SDS 81 0001, asking why email traffic on the
312111 - DKR project is "quiet"?
312112 - ..
312113 - Eugene says today...
312114 -
312115 - 1. There has been a lot of stuff going on. ref DRT 1 QH5O
312116 -
312117 - [On 000929 called Doug. ref SDS 83 0001
312118 -
312119 - 2. Design.
312120 -
312121 - a. There were several one-on-one design discussions, which
312122 - were very valuable. ref DRT 1 PH6J
312123 -
312124 - Eugene does not identify these meetings nor the results. In
312125 - a second letter received later in the AM, Eugene responds
312126 - to a request for summaries of the meeting with Doug on the
312127 - OHS design. ref DRT 2 0001
312128 -
312129 - Some DKR contributors reported separately in the record the
312130 - following meetings...
312131 -
312132 - On 000824 Eric Armstrong reported meeting with Doug.
312133 - ref SDS 63 0001
312134 -
312135 - On 000825 Bryon Lincoln reported on meeting with Doug.
312136 - ref SDS 65 0001
312137 -
312138 - On 000828 Grant Bowman reported on meeting with Doug.
312139 - ref SDS 67 L52W
312140 - ..
312141 - b. Eric has produced a document on email deficiencies --
312142 - and it's a doozy -- to follow up design discussions.
312143 - ref DRT 1 5A6N
312144 -
312145 - Email deficiencies are further set out in anlaysis on the
312146 - high cost of medical mistakes, ref DIP 1 1045, developed on
312147 - 990924. ref SDS 11 0715
312148 -
312149 - Need explanation of how to correct defects in email that
312150 - permeate other communications like meetings, calls reading
312151 - a book, a memo, magazine article, etc. What is the
312152 - solution for email that helps other knowledge work?
312153 - ..
312154 - c. The team has developed a working (Augment->HTML)
312155 - script. This is helpful on two levels. ref DRT 1 009I
312156 -
312157 - 1. Doug will be able to dump old Augment design notes and
312158 - source code onto the Web. He'll also be able to
312159 - generate new notes and comments from Augment, and have
312160 - them dumped onto the Web automatically. Look for this
312161 - starting next week. ref DRT 1 SG7L
312162 -
312163 - [On 001006 progress on Augment translator. ref SDS 86 0001
312164 -
312165 - [On 001017 Doug plans to put Augment docments on the Internet.
312166 - ref SDS 90 PC8J
312167 -
312168 - [On 001025 Doug confirms this task is pending. ref SDS 92 V9S1
312169 -
312170 - 2. A lot of the pending work on this system can be used as
312171 - the basis for the system at large. ref DRT 1 PG8G
312172 -
312173 - d. In a second letter received today, Eugene cites progress
312174 - reported by another contributor...
312175 -
312176 - I'm mostly poking at the Augment linking conventions
312177 - and file structures, trying to figure out what those
312178 - portend for DKRs. Still without the actual Augment
312179 - client, I haven't devoted as much time to thinking
312180 - about views and user commands. ref DRT 2 QN6L
312181 -
312182 -
312183 - e. Nicholas has developed a great design for the OHS web
312184 - pages, which we'll hopefully get up relatively soon.
312185 - ref DRT 2 004Y
312186 -
312187 - When will design be available for review? What criteria
312188 - were used for the design?
312189 - ..
312190 - f. Sheldon has been mocking up some images of what the
312191 - system might look like; Eugene is looking forward to seeing
312192 - results. ref DRT 2 JP8K,
312193 -
312194 - This confirms report on 000818 that work is underway on
312195 - mock ups. ref SDS 61 JH7K
312196 -
312197 - What progress has occurred on mock ups the past 40 days?.
312198 -
312199 - Can we see a preliminary mock up, one that is partially
312200 - complete to assess progress and suggest ideas? What
312201 - team input has informed current mock up work?
312202 -
312203 - [On 001010 Sheldon reports a couple of mock up screens
312204 - are complete, and annotations are in progress.
312205 - ref SDS 87 416L
312206 -
312207 - 3. Funding.
312208 -
312209 - We've gotten very strong feedback from DARPA and NIH, and are
312210 - in the process of developing formal proposals. We'll know more
312211 - within the next few weeks. ref DRT 1 005I
312212 - ..
312213 - 4. Project Deliverables Not Commonly Understood
312214 -
312215 - One of the previous problems we had was that the group did not
312216 - have a common picture of what we're trying to achieve. This
312217 - was the reason we split off into smaller sessions in the first
312218 - place -- to work out these issues once and for all. I think
312219 - we've accomplished this, but our next challenge is to
312220 - disseminate this information to the rest of the group.
312221 - ref DRT 1 NW9F
312222 -
312223 - [On 001017 Eugene reported architecture is not yet
312224 - established. ref SDS 90 TJ3G
312225 -
312226 - [On 001221 Gary Johnson says progress is slow because DKR
312227 - team has not set a clear course. ref SDS 93 0159
312228 -
312229 - This point is re-stated in a second letter. ref DRT 2 006X
312230 -
312231 - On 000324 project planning showed need to define mission.
312232 - ref SDS 25 9776 and deliverable. ref SDS 25 5964
312233 -
312234 - Eugene's report today supports team meeting on 000615 that
312235 - disclosed Knowledge Management is difficult to understand.
312236 - ref SDS 47 6271
312237 -
312238 - Eugene's letters do not explain the common picture that has
312239 - been achieved of the deliverable, nor explain where this is
312240 - set out in the record, nor indicate who has the "common
312241 - picture" and when it will be presented. Neither is there an
312242 - explanation of factors that delay disclosure.
312243 -
312244 - On 000503 Eric Armstrong reported that knowledge repository
312245 - is unclear. ref SDS 31 5033 and ref SDS 31 0672
312246 -
312247 - On 000824 Eric Armstrong reported that Doug proposes an
312248 - architeture for the OHS that is based on the Rod Welch
312249 - system. ref SDS 63 PU5N SDS on the Internet is an example
312250 - of a deliverable that goes beyond traditional information
312251 - systems, and interacting with the record over weeks and
312252 - months, illustrates how technology can aid knowledge work,
312253 - noted by Henry van Eykan on 000926. ref SDS 80 IP7F
312254 -
312255 - [On 001012 Grant Bowman reports meeting with Doug showing
312256 - common vision for OHS. ref SDS 88 K49J
312257 -
312258 - Eugene says that obviously, before everyone has a clear picture
312259 - of our objectives and what the system is going to look like, it
312260 - makes it difficult to start contributing. However, if you're
312261 - just rarin' to go, I'd encourage you to push the issue, and
312262 - start asking questions about the system or a piece of the
312263 - system, rather than wait for someone to decree what you should
312264 - be doing. We started having some of these discussions several
312265 - months ago regarding categorization, the hyperdocument, and
312266 - other important issues, but they died relatively quickly. All
312267 - of these are vital things to work out, and so if you're looking
312268 - for things to start working on, start with those. ref DRT 1
312269 - 00EJ
312270 - ..
312271 - 5. Team members can take the initiative to begin producing
312272 - pieces of project deliverables. ref DRT 2 IS9I
312273 -
312274 - Need list of tasks and WBS scope to aid folks in beginning
312275 - production work.
312276 -
312277 - [On 001004 letter to Eric requests rough schedule.
312278 - ref SDS 25 2640
312279 -
312280 - [On 001010 Sheldon has started mock ups. ref SDS 87 416L
312281 -
312282 - [On 001012 Grant Bowman anxious to get started, even if not
312283 - in the correct direction. ref SDS 88 B4P2
312284 -
312285 - [On 001017 vision for architecture not yet established,
312286 - ref SDS 90 TJ3G; new project manager to select core
312287 - development team for production to begin in 2001.
312288 - ref SDS 90 01EY
312289 -
312290 - [On 001017 Eric Armstrong reports code for OHS started, and
312291 - architecture makes sense. ref SDS 89 0001
312292 -
312293 - [On 001018 Eric reports snag in architecture. ref SDS 91
312294 - GD6J
312295 -
312296 -
312297 -
312298 -
312299 -
312300 -
312301 -
Distribution. . . . See "CONTACTS"