Click here to comment!
1...Missing element in CDS (OHS) developed by Eric for DKR project
2...Would help to get some alignment between this objective and
3...Need explanation of source, purpose, and linkes to authority, and/or
4...Need version number on OHS minimum elements.
5...Need correlation with links showing where these "minimum" elements are
6...This information needs to be analysed and correlated with DKR project
7...Attribution and credit seem to be missing, which may be a helpful
8...Has Hyperdoc Library been used and/or reviewed anywere?
9...Who maintains the record, what procedures for backing up,
Open Source Development Freeware
Attribution Credit, Links to Original Sources of Contributions, Sporh
Editor Development v0.8, 000605
DDOM Updates Changes to Specs Autmatically, 000605
Update Automatically Incorporate Changes to Specs, DDOM, 000605
Changes Automatically Incorporate in Specs, DDOM, 000605
DOM, Direct, JDOM Processors of XML DKR, 000427
Editor Development v0.9, 000614
2210 - ..
2211 - Summary/Objective
221201 - Follow up ref SDS 80 0000, ref SDS 78 0000.
221203 - Eric's has done a terrific job putting the project specs into HTML. He
221204 - did not have time to detail changes and provide pointers for review,
221205 - per procedures set up for v0.7 and v0.8. As a result, could not focus
221206 - review, nor develop alignment and feedback. ref SDS 0 3116 Current
221207 - specs provide a link to priorities on Bootstrap; there was not enough
221208 - time for correlation nor alignment between priorities and project
221209 - specs. ref SDS 0 0789 A new resource showing OHS minimum elements is
221210 - provided by reference; needs engineering management. ref SDS 0 5296
221211 - Eric offers helpful ideas for engineering management on the Wiki
221212 - effort, which will require disclipline and will be tricky. ref SDS 0
221213 - 0895 IBIS is proposed to address the issue. ref SDS 0 4939 He says
221214 - contributors will have to "play DKR" and does not review the level of
221215 - effort this entails. Eric reviews Bootstrap plan to improve software
221216 - programming, and suggests continued focus on CDS, as generic
221217 - enhancement of capabilities that will improve programming and other
221218 - crafts.
221220 - [On 000615 Eugene proposes calling CDS the OHS. ref SDS 85 2808
221222 - ..
221223 - [On 000711 SRI submits pre-proposal to NASA for OHS. ref SDS 90
221224 - 0001
221228 - ..
2215 - Progress
221601 - ..
221602 - Editor Specification Needs Alignment with Architecture
221603 - CDS v0.9 Requires Alignment to Reduce Boggling the Mind
221605 - Follow up ref SDS 80 0782, ref SDS 78 0782.
221607 - Received ref DRT 1 0001 from Eric commenting that v0.9 of the CDS
221608 - (also OHS) specs are now located on his web site....
221611 - ..
221612 - http://www.treelight.com/software/bootstrap/requirements.html
221615 - ..
221616 - Which for convenience is put in ref DRT 2 0001.
221618 - [On 000615 Eugene proposes calling CDS the OHS. ref SDS 85 2808
221620 - [On 001010 notice of using lens possibly for view control, and
221621 - user interface to apply efficient Augment control methods.
221622 - ref SDS 95 G8R3
221624 - ..
221625 - [On 001015 Eugene reports Eric's specs have been reviewed and
221626 - comments will be issued on 001030. ref SDS 96 RI9J
221628 - ..
221629 - [On 001017 Eric reports production of OHS is underway.
221630 - ref SDS 97 0001
221632 - ..
221633 - This v0.9 on the web shows Eric as the author, but it is undated, and
221634 - so lacks effective utility.
221636 - ..
221637 - Related links include...
221639 - 1. OHS minimum elements. ref SDS 0 5296
221641 - ..
221642 - 2. OHS Framework based on Doug Engelbart's Bootstrap Work
221644 - Missing element in CDS (OHS) developed by Eric for DKR project
221645 - is a section that correlates Engelbart's OHS Framework.
221647 - ..
221648 - 3. Eric's Review of Doug Engelbart's NSL System
221650 - This is dated 000622, but is linked here, so is a little out
221651 - of sync with submission today of v0.9 CDS specs.
221653 - ..
221654 - 4. XML Data Structure List
221657 - ..
221658 - A table of contents/summary is at...
221661 - http://www.treelight.com/software/bootstrap/requirements_TOC.html
221664 - ..
221665 - Eric says the following are changed, ref DRT 1 5244, added or deleted
221666 - to create v0.9...
221668 - Reformatting and linking, minor edits.
221669 - Improved the picture of development-document cycles.
221670 - Appended a new paragraph to "Partionable"
221672 - ..
221673 - There is not an explanation of changes, nor is there a link to the new
221674 - section, and to the prior version to show the changes, as was done for
221675 - v0.8 received on 000605. ref SDS 80 0782
221677 - ..
221678 - Eric does not respond to the letter, ref DIP 3 0001, asking about
221679 - disposition of Data Structures, other than incorporating into
221680 - Requirements, submitted on 000605. ref SDS 80 0001
221682 - ..
221683 - Inspection seems to indicate this material has been put a web page
221684 - with the title of XML Data Structures....
221687 - http://www.treelight.com/software/bootstrap/dataStructures.html
221690 - ..
221691 - Inspection also shows quite a number of changes in ref DRT 2 0001,
221692 - which Eric does not have time to specify, and this evening I do not
221693 - have time to chase down. It would simple enough for an author to jot
221694 - down the changes and provide links to the changes, as Eric reported
221695 - he did on a project in Texas, when we met at Intel on 000517.
221696 - ref SDS 76 2064
221698 - ..
221699 - As a result, could not develop alignment in this review within the
221700 - time available, which conflicts with objectives of requirements
221701 - reported on 000601, ref SDS 78 4997, and shown in the current v0.9
221702 - received today. ref DRT 2 5814
221704 - ..
221705 - There is no discussion of issues cited in the record on 000505,
221706 - ref SDS 71 0001, submitted to the DKR team on 000515, reviewing the
221707 - requirements in depth. ref SDS 75 0001
221709 - ..
221710 - Update the Record for DKR
221711 - DKR Management Process Updates the Record
221713 - Follow up ref SDS 80 5084.
221715 - The procedure Eric explained on 000605 for v0.8 and was also
221716 - needed for version 0.7, is not applied to this update for v0.9,
221717 - and the lack of explanation of changed, makes it impossible to
221718 - update the specs.
221720 - ..
221721 - Eric's letter transmitting v0.7 on 000601, ref SDS 78 0782, and
221722 - the letter transmitting changes for v0.8 on 000605, identified
221723 - changes and advised team members to perform the DKR role by
221724 - integrating the changes into the prior versions to create
221725 - updates. ref SDS 80 5084
221727 - ..
221728 - Eric's letter today explains how to implement DKR procedures for
221729 - the Wiki system, ref DRT 1 2160, reported by Lee Iverson on
221730 - 000609. ref SDS 84 0001
221732 - ..
221733 - However, the submissions received today for v0.9 abandon the
221734 - prior procedure, and leave receipients to guess when and to what
221735 - extent changes have been made.
221738 - ..
221739 - XML Data Structures are in a separate page...
221742 - http://www.treelight.com/software/bootstrap/dataStructures.html
Priority Vectors, Bootstrap, 000614
Priorities, Bootstrap, Continuous Arching Priority, Engelbart, 000614
Build DKR by Bootstrapping
Augment Human Capabilities
260801 - ..
260802 - Immediate Priority Linked to Doug's Bootstrap Web Site...
260806 - http://www.bootstrap.org/alliance/wip/unrev2/current_priorities.html
260809 - ..
260810 - Thus supplements Bootstrap mission reviewed on 991222. ref SDS 13 3495
260812 - ..
260813 - This is a good start on implementing alignmet incorporated into the
260814 - OHS (CDS) requirements on 000601, ref SDS 78 4997, but need to get
260815 - details in the requirements linked back and forth to priorities for
260816 - effective Communication Metrics and sound engineering management,
260817 - reported by Eric on 000517. ref SDS 76 2064
260820 - ..
260821 - Under a heading...
260823 - ..
260824 - Continuous Over-arching Priority
260826 - "We need to augment the human capability infrastructure which
260827 - supports the collective IQ of any group dealing with any issue
260828 - (governmental, educational, business etc) and in particular
260829 - through improving the improvement infrastructure."
260831 - ..
260832 - Ie. Things are changing faster and faster so we need to work
260833 - together to cope well.
260835 - ..
260836 - Doug Engelbart
260838 - Would help to get some alignment between this objective and
260839 - where it is carried out in the project specs, per call for
260840 - "alignment" in v0.9. ref SDS 0 1664 and on 000601.
260841 - ref SDS 78 4997
Priority Vectors, Bootstrap, 000614
Priorities, Bootstrap, Continuous Arching Priority, Engelbart, 000614
Build DKR by Bootstrapping
Bootstrap Strategies, 000227
300801 - ..
300802 - General, Specific Project Priority:
300804 - Build a Dynamic Knowledge Repository by bootstrapping, ie.
300805 - using what we can get at any point to get close to what we
300806 - want.
300808 - http://www.bootstrap.org/alliance/wip/unrev2/current_priorities.html
300810 - ..
300811 - Team has not yet defined what is wanted, as shown on
300812 - 000503, ref SDS 67 5033, and so is having difficulting
300813 - deciding what to use in order to "get close" to an
300814 - undefined objective.
300816 - ..
300817 - On 000509 Paul Fernhout reivewed Bootstrap strategy.
300818 - ref SDS 73 4514
300820 - ..
300821 - [On 000615 team reviews Bootstrap methodology. ref SDS 85
300822 - 9622
300824 - ..
300825 - [On 000615 team deferring work on DKR because not enough is
300826 - known about knowledge and knowledge management. ref SDS 85
300827 - 6271
Develop Better Disscussion Methods
People Get More Involved
Write DKR Specification
Email OHS/DKR Starter Technologies Develops Experience to Create KM
Email Enhancement Hackable Program, 000428
Email Enhancement Tools, Hackable, 000428
Email Hyperdocuments Integrate
411101 - ..
411102 - Immediate Priorities:
411104 - Develop a better way to discuss how to go about this.
411106 - Reflects priority cited by Doug on 000326 to improve email.
411107 - ref SDS 53 5972 and on 000601. ref SDS 77 2760
411109 - ..
411110 - On 000609 team began using Wiki to experiment with a
411111 - connected environment. ref SDS 84 0001
411113 - ..
411114 - [... below, Eric offers ideas on using Wiki.
411116 - ..
411117 - Get more people involved.
411119 - ..
411120 - Write a DKR Specification.
Priorities, Bootstrap, Continuous Arching Priority, Engelbart, 000614
Closer collaboration Development Improvement Infrastructures
430601 - ..
430602 - Desired Outcome:
430604 - Closer collaboration in development of improvement
430605 - infrastructures.
ZWiki-style Collaborative Document System, 000427
Existing Capability, Start with What is Available, 000302
Pilot Test New Capabilities, 000227
Pilot Test Email for Organizing and Thought Tracking, 000428
DKR Starter Technologies, Email, Begin Using a System, 000504
Wiki Comment Procedures, 000614
IBIS for Wiki Comment Procedures Require Discipline, Tricky, 000614
Wiki Comment Procedures Require Discipline Play DKR, Tricky, Risky, 0
Comment Procedures Wiki Require Discipline Play DKR, Tricky, Risky, 0
Tricky Comment Procedures Play DKR for Wiki, Risky, 000614
Discipline Required Play DKR for Wiki, Risky, 000614
Play DKR Engineering Management Takes Discipline, Risky, 000614
Engineering Management Tricky Require Discipline, Risky, 000614
Risky Comment Procedures Play DKR for Wiki, Tricky, 000614
Demand Hindered Limited Time Diligence Disclipline Accountability Def
Wiki Requires Contributor to Play DKR, Eric Armstrong
861901 - ..
861902 - Hard Work Required for Knowledge Management, Tools Makes It Easier
861903 - Comment Methods for Wiki Require Discipline, Tricky, Risky
861904 - Engineering Management Procedures for Wiki Require "Playing DKR."
861905 - Wiki Email Collaboration Procedures for Comment Tool Tricky, Risky
861907 - Follow up ref SDS 84 0001.
861909 - Eric offers suggestions on using the Wiki web site as a comment tool.
861910 - People would not expect to edit the file directly, but would offer
861911 - either comments or suggestions, evaluations and selections putting
861912 - their name in each paragraph. ref DRT 1 5083
861914 - This addresses some engineering management requirements reported
861915 - on 000609, ref SDS 84 1008, and recommended in the letter to the
861916 - team, ref DIP 4 1394, submitted following review on 000609.
861917 - ref SDS 84 4588
861919 - ..
861920 - [On 000623 Jack Park suggests ideas for a Com Manager type role to
861921 - support the DKR. ref SDS 87 0784
861923 - ..
861924 - [On 000703 Morris objects to changing orginal work. ref SDS 89
861925 - 6030
861927 - ..
861928 - Eric proposes that Wiki contributors each play DKR, ref DRT 1 2160,
861929 - and that the procedure requires discipline, ref DRT 1 6138; it is a
861930 - bit tricky, ref DRT 1 0658, which leads to a risky process.
861932 - ..
861933 - Eric does not mention the hard work required to "play DKR," which was
861934 - cited in a reference noted by Doug Engelbart in his letter to the team
861935 - on 000307. ref SDS 50 5182 Given the limited time evident from lack
861936 - of alignment and pending issues on prior versions of Eric's submittal
861937 - today, per above, ref SDS 0 9009, and given that Eric is without doubt
861938 - one of the most conscious engineers on the planet, it appears
861939 - problematic at best that other contributors will have time to "play
861940 - DKR."
861942 - [On 000727 difficulites reported using Wiki. ref SDS 92 9000
861944 - ..
861945 - [On 000812 Eric reports difficulties using Wiki. ref SDS 93 1596
861947 - ..
861948 - [On 000926 Henry van Eykan worries that adding intelligence to
861949 - management takes too much diligence. ref SDS 94 004M
861951 - ..
861952 - [On 001025 Doug asks DKR project contributors to play DKR by using
861953 - links in the OHS launch plan. ref SDS 98 00VU
861955 - ..
861956 - [On 001026 Doug reports SDS record has links to the OHS launch
861957 - plan. ref SDS 99 0001
861959 - ..
861960 - [On 010218 attribution may be difficult using wiki, causes social
861961 - pathologies. ref SDS A2 FC6L
861963 - ..
861964 - On 000517 Eric related the one time that he played DKR on a project in
861965 - Texas this was helpful; but, there is only one report of such a
861966 - Hurculean effort. ref SDS 76 2064
861968 - ..
861969 - On 990527 there was a report that engineers don't like to "play DKR,"
861970 - they don't want to do engineering management; they just want to do
861971 - technology. ref SDS 7 0966 They want somebody else to do the DKR
861972 - management stuff.
861974 - ..
861975 - Just as managers and executives don't want to manage, reported by
861976 - Fortune on 990625, ref SDS 10 1024, just as doctors don't want to do
861977 - medical management, and contractors don't like to do construction
861978 - management, because management day-in-and-day-out is hard work, it
861979 - takes discipline and it is not fun, as noted by Andy Grove in his
861980 - book, Only the Paranoid Survive, reviewed on 980307. ref SDS 6 3101
861982 - ..
861983 - The DKR team might note the admonition of Covey who cautions that it
861984 - is difficult for people to learn good work habits, when they have
861985 - already acquired bad work habits, and feel comfortable with them,
861986 - reviewed on 921205. ref SDS 1 8955 People tend to explain away the
861987 - need to change work practices or hire a bunch of people (admin,
861988 - lawyers, consultants) to fix the problems they cause so they don't
861989 - have to change work habits.
861991 - ..
861992 - The purpose of OHS tools, then, is to empower people to accomplish
861993 - engineering management through the DKR, or more simply, support sound
861994 - management practice, faster, better and cheaper, so that it takes less
861995 - discipline, is less tricky, and perhaps is fun for some because it is
861996 - so easy to make the connections of cause and effect that constitutes
861997 - knowledge. Since some people prefer to know, rather than rely on
861998 - guess and gossip, hunch and hope, making it easier to generate useful
861999 - "intelligence," means we can grow more knowledge, in the same way that
862000 - farmers grow more food, and this will, over time, solve world problems
862001 - and lift civilization to a new plateau, just as an earlier technology
862002 - called the alphabet began doing about 2000 years ago.
IBIS for Wiki Comment Procedures,
Wiki DKR Manage Comment Procedures,
IBIS Decision Support
Structure Discussion from Catagorizing IBIS Links, Eugene, 000622
IBIS Catagories Structured Discussion, Eugene, 000622
920801 - ..
920802 - IBIS Procedures Proposed for Specific Evaluation Catagories
920804 - Follow up ref SDS 79 6720, ref SDS 71 2650.
920806 - We need to start moving in an IBIS kind of direction. For example,
920807 - each requirement is, in effect, a "possibility" for the system. So
920808 - each requirement should see these kinds of additions:, ref DRT 1 6138
920810 - [On 000622 Eugene supports Eric's call to use IBIS;
920811 - proposes catagorizing links and or nodes. ref SDS 86 6204
920813 - ..
920814 - [On 000630 Jack supports IBIS for DKR argumentation.
920815 - ref SDS 88 2040
920817 - ..
920818 - [On 000716 Joe Ransdell cautions about distinction between
920819 - formal logic and practical reasoning. ref SDS 91 2200
920821 - ..
920822 - [On 060129 Jeff Conklin developed IBIS; he introduced
920823 - himself at an event for Doug Engelbart's 81st birthday at
920824 - Stanford. ref SDS A4 7H7G
920826 - ..
920827 - On 000212 IBIS proposed for DKR. ref SDS 25 9282
920829 - ..
920830 - On 000218 concerns about IBIS cited. ref SDS 27 7050
920831 - ..
920832 - On 000223 Eric provided procedures for using IBIS.
920833 - ref SDS 35 4722
920835 - Can these be applied to support Wiki?
920837 - ..
920838 - On 000505 IBIS incorporated into OHS requirements. ref SDS 71
920839 - 2650
920841 - ..
920842 - On 000602 Jack Park supports IBIs requirements for OHS specs.
920843 - ref SDS 79 6720
920845 - ..
920846 - Evaluations
920848 - (this is brilliant / this is dumb)
920850 - ..
920851 - Votes
920853 - (need this right away / need to defer this)
920855 - ..
920856 - Rationale
920858 - (functionality needed / hard to add later)
920860 - ..
920861 - Comments
920863 - (just some notes)
920865 - ..
920866 - Arguments
920868 - (pro/con)
920870 - ..
920871 - Questions
920873 - (why? where? when?)
920875 - ..
920876 - Additions
920878 - (you forgot this one, dummy...)
920880 - ..
920881 - Suggestions
920883 - (I would say it this way...)
Software Programming Initial Objective, 000406
Tools to Support Writing Software
Programmers Resist Using New Tools, 000614
Risist Change Improved Work Practices
Change Resisted, Feared
Programmers Resist Changing Software Tools, 000413
Engineers Resist Changing Work Practices, 000413
People Resist Changing Methods
Software Engineers Resist Using New Tools
Email Good Target for OHS/DKR to Support Software Engineers
A11501 - ..
A11502 - Software Programming Planned Initial Product; No Progress So Far
A11504 - Follow up ref SDS 83 7238.
A11506 - Received ref DRT 4 0001 from Eric on progress to improve software
A11507 - programming, discussed at SRI meeting on 000608. ref SDS 83 7238
A11509 - ..
A11510 - Eric notes that CDS requirements, while supportive of communication
A11511 - for software programming, does not contain any specific provisions for
A11512 - this objective; and, in fact avoids software management completely.
A11513 - ref DRT 4 0605
A11515 - ..
A11516 - Eric notes that software programming support entails complexities that
A11517 - are unique to software support. ref DRT 4 1302
A11519 - [On 000615 team meeting at SRI on DKR development does not discuss
A11520 - software development. ref SDS 85 7238
A11522 - ..
A11523 - Eric observes that software-designers are included among the people
A11524 - who could use a good online discussion tool. ref DRT 4 2516
A11526 - Possibly, the people who need a good discussion tool, might feel
A11527 - too constrained by limiting the aid to just discussion, when in
A11528 - fact they need a tool for all of their thinking needs, where it
A11529 - helps to add "intelligence" to information.
A11531 - ..
A11532 - Since Doug is promoting the idea of "intelligence" in Bootstrap's
A11533 - priorities, cited by Eric in the v0.9 specs today, ref SDS 0 4396,
A11534 - (and previously in his 1992 paper reviewed on 991222, ref SDS 13
A11535 - 8064), perhaps the team can add "intelligence" to management, and
A11536 - since discussions are part of management, this would work for
A11537 - engineering management to help the software engineer. It would
A11538 - equally help the mechanical, electrical, HVAC, biology, automotive
A11539 - and all other engineers. It would help the banker, the baker,
A11540 - carpenter, physicist, chemist, accountant. Intelligence could help
A11541 - doctors and patients improve medical management so there are fewer
A11542 - mistakes that cause death and mayhem, ref DIP 1 0001, reported on
A11543 - 990924. ref SDS 11 0001
A11545 - ..
A11546 - We can not only help discussion, but also support analysis to
A11547 - prepare for discussion, and aftward to discover what was missed
A11548 - during the discussion. Ee don't have to stop with discoverying
A11549 - the mistakes in discussions, we can discover our mistakes in our
A11550 - specs, and performance of daily work, so we can take proactive
A11551 - corrective action to mitigate damage.
A11554 - ..
A11555 - Programmers Like Familiar Tools, So Do Executives, Doctors, Plumbers
A11557 - Eric explains that for many software folk, you will only pry emacs
A11558 - (vi, or what-have-you) "from their cold, dead fingers". So they are
A11559 - going to be less than excited about some new way to edit their
A11560 - software. (But making sure that software goes both ways between plain
A11561 - text and the system _without_ _losing_information_ is what creates
A11562 - most of the complexity.), ref DRT 4 5561
A11564 - ..
A11565 - On 000413 Software Carpentry project reported programmers don't like
A11566 - to use new tools. ref SDS 58 2124
A11568 - On 990525 report engineers don't like to use engineering
A11569 - management that requires writing. ref SDS 7 0966
A11571 - On 990527 Andy Grove reports engineers don't like to read either.
A11572 - ref SDS 8 5110
A11574 - ..
A11575 - On 000420 Crit team was reported to have ignored the tools they
A11576 - created, and used familiar email to communicate. ref SDS 60 4911
A11578 - ..
A11579 - On 000227 Eric anticiapted software projects would be a good place to
A11580 - Bootstrap awareness of advantages planned for the DKR. ref SDS 40 1248
A11582 - ..
A11583 - On 980307 Andy Grove notes that people like to work on familiar things
A11584 - in familiar ways. ref SDS 5 3740
A11587 - ..
A11588 - Programming Improvements Attracts Programmers, Bootstraps Apps
A11590 - Eric cites following reasons for pursing software programming
A11591 - capabilities...
A11593 - a. We are only designing to make sure the data structures are
A11594 - appropriate, but we don't plan to implement any of this.
A11595 - ref DRT 4 9894
A11597 - ..
A11598 - b. Open Source developers and organizations we know have told us
A11599 - they want this. ref DRT 4 5883
A11602 - ..
A11603 - Asks if there are other reasons?
A11605 - On 000406 Lee Iverson and Eugene Kim indicated that developing a
A11606 - stronger software programming capability would attract a wide
A11607 - circle of programmers to the Bootstrap Open Source effort. This
A11608 - aligns with priority set by Doug to increase the people involved in
A11609 - the project, ref SDS 0 7483, who can develop programs faster to
A11610 - solve world problems. ref SDS 56 5078 On 000601 Warren Stringer
A11611 - supported this analysis. ref SDS 77 7238
A11613 - ..
A11614 - There is no evidence in the record showing how many programmers
A11615 - would be attracted by better tools, or if and when better software
A11616 - programming tools can be produced.
A11618 - ..
A11619 - On 000601 Doug Engelbart proposed that multiple views for software
A11620 - programmers would be helpful for other uses. ref SDS 77 7238
A11622 - [On 000615 team meeting at SRI on DKR development does not
A11623 - discuss software development. ref SDS 85 7238
A11625 - [...meeting of DKR team at SRI reviewed Bootstrap process and
A11626 - did not discuss software programming. ref SDS 85 9622
OHS Minimum Requirements, 000614, Eric Armstrong
OHS Min Elements, v0.1, 000614
Minimum Elements Requirements, 000614
Mixed Object Docs, 000614
Technology Template Project Defines OHS, DKR, Doug Engelbart 980128
Technology Template Project Defines OHS, DKR, Doug Engelbart, 980128
A80901 - ..
A80902 - OHS Minimum Elements Need Identification, Version Control
A80904 - There is a link in CDS Requirements v0.9 received above, ref SDS 0
A80905 - 0782, to another address....
A80908 - http://www.bootstrap.org/alliance/wip/unrev2/min_req_ohs.html
A80911 - ...with the title...
A80914 - ..
A80915 - Minimum Elements of an OHS
A80917 - ..
A80918 - There is no name and no date for identification of OHS minimum
A80919 - requirements.
A80921 - [On 000615 no discussion of minimum elements during meeting at
A80922 - SRI on OHS vector. ref SDS 85 5880
A80924 - ..
A80925 - Need explanation of source, purpose, and linkes to authority, and/or
A80926 - record that supports or illustrates the meaning and application of
A80927 - terms presented.
A80929 - ..
A80930 - What experience supports the representations about usefulness of
A80931 - proposed "elements"?
A80933 - ..
A80934 - Need version number on OHS minimum elements.
A80936 - ..
A80937 - Need correlation with links showing where these "minimum" elements are
A80938 - incorporated and expanded into the larger CDS spec.
A80940 - ..
A80941 - Bootstrap OHS Framework is also referenced and identified as...
A80943 - ..
A80944 - BOOTSTRAP ALLIANCE
A80946 - TECHNOLOGY TEMPLATE PROJECT 0
A80948 - OHS Framework
A80950 - Version 2 (28-Jan-98)
A80951 - (ALLIANCE,980,)
A80954 - ..
A80955 - http://www.bootstrap.org/alliance-980.htm
A80958 - ..
A80959 - On 000128 Clark Quinn cited this reference, ref SDS 18 6960, which
A80960 - supplements Doug's 1992 paper reviewed on 991222, ref SDS 13 3360,
A80961 - and, also, Doug's 1972 paper, reviewed on 000327. ref SDS 54 3971
A80963 - [On 001115 Eric does not recall seeing documents that explain
A80964 - OHS and DKR scope. ref SDS A0 895L
A80966 - ..
A80967 - [On 030111 Eric asks for support to find OHS specs. ref SDS A3
A80968 - YN71
A80970 - ..
A80971 - Technology Template Project discusses...
A80974 - OHS covers commercial and research tools that can be designed,
A80975 - implemented, and evaluated. "Hyperdocument" implies flexible
A80976 - linkages to any object in any multi-media file. "Open" implies
A80977 - vendor-independent access to the hyperdocuments within and
A80978 - across work groups, platforms, and applications. 1A
A80981 - ..
A80982 - http://www.bootstrap.org/alliance-980.htm#0272
A80985 - ..
A80986 - OHS defines low level content and structural elements of a
A80987 - Hyperdocument File System; the means for accessing, navigating,
A80988 - linking, manipulating, and portraying these elementary objects;
A80989 - the basic services, applications, and utilities built from
A80990 - these elements and methods; through end user systems
A80991 - constructed from and interacting with the lower level elements
A80992 - in the hierarchy.
A80995 - ..
A80996 - http://www.bootstrap.org/alliance-980.htm#0274
A80999 - ..
A81000 - [On 001025 Doug submits OHS Launch Plan with similar features
A81001 - for Hyperscope, to be enhanced by more robust OHS, but does
A81002 - not cite his Technology Template Project paper. ref SDS 98
A81003 - A5U6
A81005 - ..
A81006 - Foundational Knowledge Environment is supported by Dynamic
A81007 - Knowledge Capture, which mentions "repository," and so may be a
A81008 - forerunner of DKR.
A81010 - http://www.bootstrap.org/alliance-980.htm#0436
A81012 - http://www.bootstrap.org/alliance-980.htm#0444
A81014 - ..
A81015 - [On 001025 Doug submits OHS Launch Plan that discusses a DKR
A81016 - that is not explained in detail, but may reflect the scope for
A81017 - Dynamic Knowledge Capture. ref SDS 98 C9WP
A81019 - ..
A81020 - [On 001116 Adam Cheyer defines DKR based on telecon with Doug
A81021 - that seems to apply Doug's 1972 paper explaining Knowledge
A81022 - Workshop. ref SDS A1 JO3F
A81024 - ..
A81025 - Thus, the Technology Template Project discusses OHS as tools, and
A81026 - implies a DKR, though not explicitly using that term.
A81028 - ..
A81029 - This information needs to be analysed and correlated with DKR project
A81030 - Requirements for OHS v0.9, received today, and with the following
A81031 - minimum elements for OHS....
A81033 - [On 000615 no discussion or review scheduled during project
A81034 - meeting at SRI. ref SDS 85 5236
A81036 - ..
A81037 - [On 001025 Doug submits OHS Launch Plan, does not cite the
A81038 - Technology Template Project document. ref SDS 98 A4U2
A81040 - ..
A81041 - [On 001115 Eric does not recall seeing documents that explain
A81042 - OHS and DKR scope. ref SDS A0 895L
A81045 - ..
A81046 - Mixed-Object Documents
A81048 - to provide for an arbitrary mix of text, diagrams, equations,
A81049 - tables, raster-scan images (single frames, or even live video),
A81050 - spread sheets, recorded sound, etc -- all bundled within a common
A81051 - "envelope" to be stored, transmitted, read (played) and
A81052 - printed as a coherent entity called a "document." ref DRT 3 8372
Mixed Object Docs, 000614
Explicitly Structured Docs, 000614
Structured Notes, Discussion
Structured Discussion Catagorize Nodes, Eugene, 000622
AC0701 - ..
AC0702 - Explicitly Structured Documents
AC0704 - where the objects comprising a document are arranged in an
AC0705 - explicit hierarchical structure, and compound-object substructures
AC0706 - may be explicitly addressed for access or manipulation of the
AC0707 - structural relationships. ref DRT 3 2915
Multiple View Control, 000614
View Control OHS Min Element, 000614
View Control OHS Min Elements, Eric, 000614
AF0601 - ..
AF0602 - View Control Of Objects' Form, Sequence And Content
AF0604 - Follow up ref SDS 83 RP4K, ref SDS 77 7238.
AF0606 - Structured, mixed-object document may be displayed in a window
AF0607 - according to a flexible choice of viewing options -- especially by
AF0608 - selective level clipping (outline for viewing), but also by
AF0609 - filtering on content, by truncation or some algorithmic view that
AF0610 - provides a more useful view of structure and/or object content
AF0611 - (including new sequences or groupings of objects that actually
AF0612 - reside in other documents). Editing on structure or object content
AF0613 - from such special views would be allowed whenever appropriate.
AF0614 - ref DRT 3 3780
AF0616 - ..
AF0617 - [On 000812 Eric Armstrong cites difficulties to maintain
AF0618 - multiple views using servletts on the server side. ref SDS 93
AF0619 - 0I6O
Basic Hyperdocument Links, 000614
Link Nodes Comprise OHS System, Eugene, 000622
Link Addressability Anchors Original Docs
Backlinks, Min OHS Elements, 000614
AL0701 - ..
AL0702 - Basic "Hyperdocument" Links
AL0704 - where embedded objects called "links" can point to any arbitrary
AL0705 - object within the document, or within another document in a
AL0706 - specified domain of documents -- and the link can be actuated by a
AL0707 - user or an automatic process to "go see what is at the other end,"
AL0708 - or "bring the other-end object to this location," or "execute the
AL0709 - process identified at the other end." (These executable processes
AL0710 - may control peripheral devices such as CD ROM, video-disk players,
AL0711 - etc.), ref DRT 3 3472
AL0713 - ..
AL0714 - Attribution and credit seem to be missing, which may be a helpful
AL0715 - minimum requirement for a workable system.
Backlinks, Min OHS Elements, 000614
AP0401 - ..
AP0402 - Hyperdocument "Back-Link" Capability
AP0404 - when reading a hyperdocument online, a worker can utilize
AP0405 - information about links from other objects within this or other
AP0406 - hyperdocuments that point to this hyperdocument -- or to
AP0407 - designated objects or passages of interest in this hyperdocument.
AP0408 - ref DRT 3 7128
AP0410 - On 000608 Doug Engelbart cited Jeff Conklin's development of
AP0411 - back link management. ref SDS 83 4725
Library Hyperdoc, OHS Min, 000614
Redundancy Storage Bumbling
Permanent Address, Xanadu
AU0801 - ..
AU0802 - Hyperdocument "Library System"
AU0804 - where hyperdocuments can be submitted to a library-like service
AU0805 - that catalogs them and guarantees access when referenced by its
AU0806 - catalog number, or "jumped to" with an appropriate link. Links
AU0807 - within newly submitted hyperdocuments can cite any passages within
AU0808 - any of the prior documents, and the back-link service lets the
AU0809 - online reader of a document detect and "go examine" any passage of
AU0810 - a subsequent document that has a link citing that passage.
AU0811 - ref DRT 3 5092
AU0813 - ..
AU0814 - Has Hyperdoc Library been used and/or reviewed anywere?
AU0816 - ..
AU0817 - Who maintains the record, what procedures for backing up,
AU0818 - maintaining access when systems fail, i.e., redundancy???
AU0820 - ..
AU0821 - How do people keep working, when DKR folks drop the ball?
Mail Hyperdoc, OHS Min, 000614
Email Core Capability DKR, Eric, 000505
AY0501 - ..
AY0502 - Hyperdocument Mail
AY0504 - where an integrated, general-purpose mail service enables a
AY0505 - hyperdocument of any size to be mailed. Any embedded links are
AY0506 - also faithfully transmitted -- and any recipient can then follow
AY0507 - those links to their designated targets in other mail items, in
AY0508 - common-access files, or in "library" items. ref DRT 3 2784
Personal Signature, OHS Min, 000614
Signature Control Authority
Owner, Secure from Change, Xanadu
B40901 - ..
B40902 - Personal Signature Encryption
B40904 - where a user can affix his personal signature to a document, or a
B40905 - specified segment within the document, using a private signature
B40906 - key. Users can verify that the signature is authentic and that no
B40907 - bit of the signed document or document segment has been altered
B40908 - since it was signed. ref DRT 3 5395
Access Control, OHS Min, 000614
Passwords Security Access Control Privacy Confidentiality
B80501 - ..
B80502 - Access Control
B80504 - Hyperdocuments in personal, group, and library files can have
B80505 - access restrictions down to the object level. ref DRT 3 6450
Link Address Human Readable, OHS Min, 000614
B90401 - ..
B90402 - Link Addresses That Are Readable and Interpretable by Humans
B90404 - one of the "viewing options" for displaying/printing a link object
B90405 - should provide a human-readable description of the "address path"
B90406 - leading to the cited object; AND, that the human must be able to
B90407 - read the path description, interpret it, and follow it (find the
B90408 - destination "by hand" so to speak). ref DRT 3 7968
Objects Addressable, All, OHS Min, 000614
Permanent Address, Xanadu
Single Address, Xanadu
Addressability Anchors Original Docs for Linking
BD0701 - ..
BD0702 - Every Object Addressable
BD0704 - in principle, every object that someone might validly want/need to
BD0705 - cite should have an unambiguous address (capable of being
BD0706 - portrayed in a manner as to be human readable and interpretable).
BD0707 - (E.g., not acceptable to be unable to link to an object within a
BD0708 - "frame" or "card."), ref DRT 3 5029
BG0401 - ..
BG0402 - Printing
BG0404 - Hard-Copy Print Options to Show Addresses of Objects and Address
BG0405 - Specification of Links
BG0407 - so that, besides online workers being able to follow a
BG0408 - link-citation path (manually, or via an automatic link jump),
BG0409 - people working with associated hard copy can read and interpret
BG0410 - the link-citation, and follow the indicated path to the cited
BG0411 - object in the designated hard-copy document. ref DRT 3 5320
BG0413 - ..
BG0414 - Also, suppose that a hard-copy worker wants to have a link to a
BG0415 - given object established in the online file. By visual
BG0416 - inspection of the hard copy, he should be able to determine a
BG0417 - valid address path to that object and for instance hand-write an
BG0418 - appropriate link specification for later online entry, or
BG0419 - dictate it over a phone to a colleague.