Click here to comment!
1...Eugene should provide an example or scenario to illustrate how
2...I've put together a lot of stuff that could be used as the basis of
CONTACTS
0201 - Bootstrap Institute 510 713 3550
020101 - Mr. Henry van Eykan; Webmaster =450 562 9618
020102 - vaneyken@sympatico.ca
SUBJECTS
Links Provided in KM Work Product Visible with Purple Numbers
OHS/DKR Requirements Use Cases Submitted With Anchors to Facilitate K
OHS/DKR Requirements Compared with Eric Armstrong Specs for CDS?
CDS Requirements Prepared by Erid Armstrong Never Reviewed
Project Management and Governance, Eugene Kim Reports No Official Sta
OHS CDS Specs Not Reviewed Nor Issued Report on 001030, as Planned on
OHS Requirements Submitted by Eugene Kim Illustrating KM with Purple
0909 - ..
0910 - Summary/Objective
0911 -
091101 - Follow up ref SDS 88 0000, ref SDS 87 0000.
091102 -
091103 - Received ref DRT 1 0001 from Eugene Kim to the OHS team, and
091104 - commenting on issues in the letter, ref DIP 4 0001, on 010201,
091105 - ref SDS 88 CM8N, responding to Eugene's letter on transition from
091106 - traditional character based literacy in China, ref DRP 4 0001, to
091107 - alphabet technology supported by IT.
091108 -
091109 - [On 010313 submitted response. ref SDS 89 0001
091110 -
091111 - Eugene initially cites the letter, ref DIP 4 1Z6O, saying.....
091112 -
091113 -
091114 - Your recent work developing requirements for an OHS helps foster a
091115 - culture of knowledge that aids the transition from IT to KM. How
091116 - do your requirements for OHS correlate with Eric's submission of
091117 - CDS specs on 000614. ref SDS 35 0782
091118 -
091119 -
091120 - ...., from the record on 010201, ref SDS 88 J34M
091121 -
091122 - ..
091123 - Eugene asks......
091124 -
091125 -
091126 - Let me be glib for a moment, and ask you the same question. How
091127 - do you think my documents correlate to Eric's CDS specs?
091128 - ref DRT 1 D96I
091129 -
091130 -
091131 - Analysis of Eugene's specs is in the record on 010131. ref SDS 87 M33O
091132 -
091133 - Eugene further says....
091134 -
091135 - There's definitely large overlap between our respective documents,
091136 - even more so than apparent, as I've shared many good design
091137 - discussions with Eric and benefitted from his insight. That's why
091138 - I singled out Eric, along with a few others, in my introduction.
091139 - ref DRT 1 WG7O
091140 -
091141 - http://www.eekim.com/cgi-bin/dkr?fn=/ohs/synopsis.html#03
091142 - ..
091143 - I made an effort to describe a smaller, but more general
091144 - system than Eric did by limiting the scope of the system somewhat,
091145 - ref DRT 1 KA8L, and by separating everything into three elements --
091146 - the.....
091147 -
091148 - Use Cases,
091149 - requirements, and
091150 - scenarios.
091151 -
091152 - Eric's specs are quite broad, and therefore offer a "general
091153 - system" that applies widely, as reported on 000505. ref SDS 30
091154 - 0001
091155 -
091156 - Eugene should provide an example or scenario to illustrate how
091157 - his system is more general.
091158 -
091159 - What limitations are evident in Eric's proposal, that are
091160 - solved by Eugene's requirements.
091161 -
091162 - On 001122 Eric Armstrong reported snags in the architecture he
091163 - is developing; a letter to Eric recommended simplyfying his
091164 - design, as the best way to launch a KM development project,
091165 - when starting from scratch, ref SDS 72 WP8H, as Eugene is
091166 - planning today.
091167 -
091168 -
091169 - Eugene's OHS requirements include Use Cases and Scenarios.....
091170 -
091171 - The first two elements are abstractions of the system. Every
091172 - requirements comes out of at least one of the Use Cases. Every
091173 - scenario can be satisfied with one or more Use Cases. The Use
091174 - Cases and requirements documents can be refined, but I think the
091175 - greatest added value is in fleshing out the scenarios document.
091176 - This will help give people a better picture of the system as a
091177 - whole. ref DRT 1 QD9G
091178 -
091179 - Scenarios provide helpful guidance on how tools can save time and
091180 - improve earnings by better handling of daily working information,
091181 - proposed by Doug Engelbart, reviewed on 000327. ref SDS 21 3971
091182 - This avoids bumbling that causes stock prices to fall due to too
091183 - many problems, that people cannot handle, reported on 001207.
091184 - ref SDS 79 V54M
091185 -
091186 - Typicaly day Scenario using SDS is an example. ref OF 2 0001
091187 -
091188 -
091189 - ..
091190 - Eugene continues....
091191 -
091192 - I've also tried to be more formal in my software design
091193 - methodology, so technical commentary and lingo, for the most part,
091194 - is outside of the Use Cases, requirements, and scenarios. Technical
091195 - stuff should go into a specification, pieces of which exist in
091196 - various documents here and there.
091197 -
091198 - I've put together a lot of stuff that could be used as the basis of
091199 - a specs document; I hope to post this later this week. ref DRT 1
091200 - LF9O
091201 -
091202 -
091203 - ..
091204 - Eugene cooborates the record on 000615 that CDS was changed to OHS
091205 -
091206 - He cites the letter on 010201 that says in part.....
091207 -
091208 - Recall that the next day, in the meeting on 000615 you proposed
091209 - that the team adopt Eric's specs, ref DIP 4 Z68N, as the OHS
091210 - requirements.....
091211 -
091212 - http://www.welchco.com/sd/08/00101/02/00/06/15/160030.HTM#LB51202
091213 -
091214 - ..
091215 - Eugene then says....
091216 -
091217 - Your records are inaccurate. At that meeting, I asked Eric why he
091218 - called his requirements "CDS" and not "OHS." His response was that
091219 - he wasn't sure if his requirements were the same as the ones for
091220 - the OHS, and that he didn't know the difference between the terms
091221 - "OHS" and "DKR." I suggested at the time that he just call his
091222 - stuff "OHS requirements" anyway, but I was in no official position
091223 - to sanction them as the "official" OHS requirements, and I'm
091224 - currently in no position to do that for my own set of proposed
091225 - requirements. ref DRT 1 VU4L
091226 -
091227 - Eugene's report of having suggested at the time of the meeting
091228 - on 000615 that Eric just call his stuff "OHS requirements"
091229 - anyway, ref DRT 1 NN5M, substantially aligns with the record.
091230 - ref SDS 36 5880
091231 - ..
091232 - Eugene's feedback coorborating the record on 000615, and
091233 - providing corrections on 001015, help refine accuracy for
091234 - effective KM, noted on 000518, ref SDS 34 O43M, citing Peirce's
091235 - work reviewed on 000515, holding that complete accuracy is not
091236 - possible, and must be continually refined. ref SDS 32 7380, to
091237 - foster a culture of knowledge for transitioning from IT to KM,
091238 - cited on 010201. ref SDS 88 4Y9O Feedback is discussed in
091239 - POIMS. ref OF 1 2200 It is also discussed in NWO. ref OF 3 0936
091240 -
091241 - [On 010313 thank Eugene for feedback. ref SDS 89 0001
091242 -
091243 - The record on 000615 indicates that Eric Armstrong attended the
091244 - meeting at SRI, and that he noted Eugene has developed a
091245 - prototype DKR, ref SDS 36 4194, which is exemplified by
091246 - Eugene's report on 010131. ref SDS 87 XZ8G Earlier on 000504,
091247 - Eugene reported to the team on his work developing a DKR.
091248 - ref SDS 29 0784
091249 -
091250 - Eugene's characterization of information in his letter today as
091251 - showing that the SDS record on 000615 is "inaccurate," is not
091252 - supported by the record.
091253 -
091254 - There is no record of Eric having made comments attributed to
091255 - him during the meeting on 000615, by Eugene's letter today. A
091256 - contemporaneous record showing the context of dialog, together
091257 - with other cooborative correspondence from Eric and others
091258 - surrounding the meeting on 000615, helps refine accuracy on
091259 - what Eric said and intended 8 months ago. The SDS record
091260 - submitted within a few days of the meeting has not been
091261 - previously corrected, and so nominally stands, with the
091262 - notation of Eugene's input today.
091263 -
091264 - For example, Eugene's report today that Eric was unsure about
091265 - the difference between OHS and DKR is supported by Eric's
091266 - letter on 000120, asking about the scope of DKR. ref SDS 16
091267 - 3002 Later on 000208 Eric requested assistance to understand
091268 - the "core" of KM capability. ref SDS 17 0001 Closer to the
091269 - meeting on 000615, on 000503, Eric was more pointed in refusing
091270 - to address "knowledge" which is central to a DKR. ref SDS 28
091271 - 5033 This context seems to support Eugene's report today that
091272 - Eric was confused about the meaning of "DKR."
091273 -
091274 - It is not clear why Eric would make a statement about whether
091275 - his CDS requirements were the same as the ones for the OHS,
091276 - since at the time of the meeting on 000615, there was no other
091277 - set of requirements for OHS, and the purpose of the project was
091278 - to develop such requirments toward preparing specs and actual
091279 - products, as Eric related on 000227. ref SDS 18 0984
091280 -
091281 -
091282 -
091283 -
0913 -
SUBJECTS
CDS Requirements Prepared by Eric Armstrong Never Reviewed
CDS V0.9, 000614
CDS Specs Pending Review, Eugene Kim
1206 -
120601 - ..
120602 - CDS Requirements Pending Review
120603 -
120604 - Eugene cites the letter, ref DIP 4 Z68N,.....
120605 -
120606 - ....and on 001015 the team had completed review, and you planned
120607 - to submit comments OA 001030......
120608 -
120609 - http://www.welchco.com/sd/08/00101/02/00/10/15/201628.HTM#L482321
120610 -
120611 - Have those comments been distributed, and are they incorporated
120612 - into your latest notice of OHS requirements? Has anything been
120613 - added or deleted?
120614 -
120615 - ....from the record on 010131, ref SDS 88 J34M, citing the telecon
120616 - with Eugene on 001015. ref SDS 54 RI9J
120617 -
120618 -
120619 -
1207 -
1208 -
SUBJECTS
OHS/DKR Team Eugene Asks for Who is Contributing in Reference Reviewi
Team Roster Contributors, Eugene Kim Requests Identification
OHS Specs Reviewed Comments to be Issued 001030, Eugene Kim
OHS Spec Not Reviewed as Reported on 010115, Eugene Kim
1907 -
190701 - ..
190702 - Team Contributing to Doug's OHS/DKR Project.....
190703 -
190704 - Eugene says.....
190705 -
190706 - This is also inaccurate. Your record states that I claimed the
190707 - "team" had "formally reviewed" Eric's requirements. Who is this
190708 - team? Who formally reviewed what? Frankly, I don't remember doing
190709 - anything associated with this project "formally." ref DRT 1 GQ3H
190710 -
190711 -
190712 - OHS/DKR team is comprised of an ad hoc group, led by Doug
190713 - Engelbart. Eugene was assigned project manager on 000511.
190714 - ref SDS 31 0784 Pat Lincoln, Director of the Computer Science
190715 - with SRI, has supported this team, along with Lee Iverson, and
190716 - Carla Wordworth, reported on 001017. ref SDS 55 01DP Jack
190717 - Park, Eric Armstrong, Howard Liu, Joe Williams, Adam Cheyer,
190718 - John Deneen, Grant Bowman, Sheldon Brahms, and others have been
190719 - strong local contributors. People like Gil Regev and Paul
190720 - Ferhnout, and more recently Gary Johnson, e.g., on 001219.
190721 - ref SDS 80 6A9N, have been key extended contributors. On
190722 - 000505 active members were proposed for reviewing Eric's CDS
190723 - specs. ref SDS 30 4864 On 000922 action items submitted to the
190724 - team showed this review was still pending, ref SDS 45 4864,
190725 - which led to calling Eugene, as Project Manager, on 001015.
190726 - ref SDS 54 RI9J
190727 -
190728 - "Formal" review in this context means greater focus than the
190729 - stream of email reparte that comprises work on the OHS project,
190730 - under "termite" management practices advanced by Paul Fernhout
190731 - on 000831, ref SDS 43 0001, and supported by Grant Bowman on
190732 - 001012. ref SDS 53 PT5M
190733 -
190734 - A formal review would entail a series of meetings to go over
190735 - the CDS specs line by line in relation to project architecture,
190736 - defined by Jack Park on 000426, ref SDS 26 0304, to adopt and
190737 - revise, or request further work, as set out in a review
190738 - document similar to the record on 000505. ref SDS 30 0001
190739 -
190740 - Today, Eugene seems to be correcting the record on what was
190741 - drawn from the telecon on 001015, indicating that a formal,
190742 - professonional, or other form of careful and deliberative
190743 - review has not occurred on Eric's CDS specs, ref SDS 54 RI9J,
190744 - contrary to the recommendation on 000505. ref SDS 30 4864
190745 -
190746 -
190747 -
190748 -
1908 -
SUBJECTS
Feedback on Submissions by Contributors is Encouraged Contributors Su
Attribution Encourages Participation, Increases Progress Open Source
Feedback Encourages Participation, Increases Chance of Getting Feedba
Feedback Critical to Communication
2307 -
230701 - ..
230702 - Feedback Reciprocal Synergy Among Contributors
230703 - Investing Time to Give Feedback Encourages Getting Feedback
230704 -
230705 - Eugene continues in his letter today....
230706 -
230707 - Let me reiterate that the stuff I have posted is an unofficial
230708 - attempt to paint a picture of the project, which could potentially
230709 - be used as the basis of a more formal set of requirements
230710 - documents. But this is not my decision to make. As I've said
230711 - before, I'd love to get feedback from other people as to whether
230712 - the picture I've pained jives with the pictures they have in their
230713 - heads. ref DRT 1 WQ3M
230714 -
230715 - Comments on Eugene's proposed OHS requirements is in the record
230716 - on 010131, ref SDS 87 XW9N, showing he requested feedback at
230717 - that time. ref SDS 87 R5T2
230718 -
230719 - Feedback is reciprocal..........
230720 -
230721 -
230722 - in order to get a return, you have to first invest.
230723 -
230724 -
230725 - ....reflecting theory of investing intellectual capital set out
230726 - in POIMS. ref OF 1 6649
230727 -
230728 - [On 010313 letter to Eugene provides cursory feedback on his
230729 - submission reported on 010131. ref SDS 89 TH5H
230730 -
230731 - Where people provide useful comments on the work, there is
230732 - greater liklihood of getting similar treatment on one's own
230733 - work. Since Eugene indicates today that feedback on Eric's CDS
230734 - specs from last June has not been developed, the basis for
230735 - obtaining review of subsequent requirements issued on 010131 is
230736 - not clear.
230737 -
230738 - Eugene indicates plans to submit more information on proposed
230739 - requirements. ref SDS 0 5H3K Perhaps feedback is being held
230740 - pending that submission.
230741 -
230742 - Disclaimer that Eugene does not speak in an official capacity
230743 - appears conflicting, for example.....
230744 -
230745 - On 000511 the record shows Eugene was assigned as Project
230746 - Manager. ref SDS 31 0784
230747 -
230748 - On 000815 Eugene reported weekly meetings at OHS were
230749 - discontinued, ref SDS 40 0001, and this occurred.
230750 -
230751 - On 001017 Eugene disclosed during a meeting at SRI that the
230752 - architecture for OHS was not established, ref SDS 55 TJ3G,
230753 - which aligns with the broader record.
230754 -
230755 - Eugene therefore appears to have a stronger voice than other
230756 - contributors within the context of the OHS project. It might
230757 - be said that open source development does not do anything
230758 - formally, as indicated by Grant Bowman on 001202.
230759 -
230760 -
230761 -
230762 -
230763 -
230764 -
230765 -
230766 -
230767 -
230768 -
Distribution. . . . See "CONTACTS"