THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net


S U M M A R Y


DIARY: February 18, 2000 08:14 AM Friday; Rod Welch

Colloquium debate, review guided by Robert's Rules of Order.

1...Summary/Objective
2...Decision Making Model Alternatives
3...Record of Communication Supports Decision Support, Supplied by DKR
4...Reporting the Record Provides "Intelligence Collection"
5...Automate Robert's Rules Guide Orderly Debate and Decision Process
6...Technology Needs Leadership to Overcome Fear of Accountability
....Technical references for Roberts Rules of Order...
....Everybody Does It
....Wide Use of RRO Support Viability of Automated System with DKR
.......Everybody Fears Accountability, Knowledge Management Dilemma
..........Cultural Differences Impede Using Robert's Rules of Order
..........Standards Imply Bias
..........Conflict Reduced by Fair Process, Consistent Standards
....OASIS - XML Vocabulary Standards
....Organization for Advancement of Structured Information Standards
....DKR Deliverable - XML Standards Knowledge Management
....Robert's Rules of Order Supported by OASIS Standards
....Plan for Automating Robert's Rules of Order
....Who Can Do It If Colloquium Automates Process?
....Parliamentary Assistant Requirements
7...Parliamentary Sessions Resolve Conflicts - Automate
8...Impasse, Conflict Resolution through Parliamentary Session
....Inaction Permits Additional Experience to Guide Decisions
9...Judicial Model of Decision Applies Experiential Record and Standards
10...Collaboration Supported by DKR Technology
11...IBIS Decision Modeling Supports Acclimation Process
12...IBIS implementation requires ability to "change" an endorsement.
13...IBIS and DKR Higher Priority than Alternative DKR and RRO
14...IBIS Rigid Rules Limit Acceptance
15...Forms in gIBIS Aid Discussion with Logically Limited Options
16...Rigidly logical rules are useful, but discourage acceptance
17...Implicit Links, Multi-links, Mouseover
18...Invisible Links in XML Editor


..............
Click here to comment!

CONTACTS 

SUBJECTS
Colloquium Unfinished Revolution, 000106
Procedures Robert's Rules of Order
Objectives Robert's Rules Automate
Decision Support, Documentation
Meetings Robert's Rules Required Records
Robert's Rules of Order Need Accurate Records for Meetings
Accurate Records SDS Better Than Tape Recording

1809 -
1809 -    ..
1810 - Summary/Objective
1811 -
181101 - Follow up ref SDS 30 0000, ref SDS 28 0000.
181102 -
181103 - Robert's Rules of Order for Parliamentary-style decision making is
181104 - reviewed for performing Colloquium objectives, ref SDS 0 0786,
181105 - including a DKR deliverable.  Need for good records is cited; DKR is
181106 - planned to support this requirement. ref SDS 0 1092  A plan for the
181107 - Colloquium to set XML standards for DKR is presented. ref SDS 0 8955
181108 - Invisible links are supported by XML that expand utility of the
181109 - Editor.  Cultural sensitivity using Robert's Rules of Order is a
181110 - factor. ref SDS 0 0783  Decision-modeling and dealing with impasse in
181111 - the Colloquium are presented. ref SDS 0 0864  Automating Robert's
181112 - Rules of Order under the name "Parliamentary Assistant," is proposed
181113 - and preliminary planning is presented, reviewing pros and cons,
181114 - relative to IBIS decision support model.  Eric recommends priority to
181115 - using IBIS, ref SDS 0 0873  He cites published analysis on lack of
181116 - acceptance for IBIS, ref SDS 0 7050, and proposes a design concept for
181117 - applying IBIS with free-wheeling email. ref SDS 0 1539
181118 -
181119 -
181120 -
181122 -  ..
1812 -
1813 -
1814 - Progress
181501 -  ..
181502 - Decision Making Model Alternatives
181503 -
181504 - Eric reports the 7th Colloquium session reviewed decision-making
181505 - models that might be implemented with technology? ref DRT 1 5550
181506 -
181507 -       [On 000225 Eric cites need to look for good systems and
181508 -       investigate augmenting. ref SDS 34 2109]
181509 -
181510 -     1.  Robert's Rules of Order
181512 -          ..
181513 -     2.  Judicial Adjudication. ref SDS 0 2912
181515 -          ..
181516 -     3.  Parliamentary Procedure, ref SDS 0 0864
181518 -          ..
181519 -     4.  gIBIS, ref SDS 0 0741
181521 -  ..
181522 - There is some confusion, from discussing automating Robert's Rules of
181523 - Order as a separate decision model from the parliamentary process. The
181524 - Parliamentary Assistant is presented as an automated application for
181525 - Robert's Rules of Order, but there seems to be a separate discussion
181526 - of automating the Parliamentary process to resolve decision stalemate.
181527 -
181528 -
181530 -  ..
181531 - Record of Communication Supports Decision Support, Supplied by DKR
181532 - Reporting the Record Provides "Intelligence Collection"
181533 - Automate Robert's Rules Guide Orderly Debate and Decision Process
181534 -
181535 - The 7th session in the colloquium included Jon Bosak's proposal to
181536 - automate Robert's Rules of Orders. ref DRT 1 4464
181538 -  ..
181539 - Eric seems to present analysis for alternate and/or complimentary
181540 - automated tools to support Robert's Rules of Order for a Parliamentary
181541 - decision model capability, explained below. ref SDS 0 9674  He says it
181542 - may be possible to co-evolve a parliamentary augmenter with a DKR.  If
181543 - not, it would seem that the a DKR/OHS/IBIS system for Open Source
181544 - Development would have higher precedence, see below. ref SDS 0 0741
181545 -
181546 -    [On 000225 John Werneken disagrees with using RRO. ref SDS 34 0987]
181548 -  ..
181549 - Eric relates Jon's analysis that DKR technology can record arguments,
181550 - decisions, and documents that result from the proceedings under
181551 - Robert's Rules of Order. ref DRT 1 2646
181552 -
181553 -       [On 000025 Eric makes this point again. ref SDS 34 0784]
181554 -
181555 -     This aligns with POIMS technology requirements for "reporting,"
181556 -     ref OF 1 2300, and with Doug Engelbart's 1992 paper on Groupware,
181557 -     proposing "intelligence collection" for knowledge management,
181558 -     reviewed on 991222. ref SDS 19 8064
181560 -      ..
181561 -     An advantage of capturing the record is case studies for lessons
181562 -     learned, and root cause analysis, reported by the U.S. Army Corps
181563 -     of Engineer received on 970418. ref SDS 10 2103  Meets ISO
181564 -     requirements for continual learning, ref SDS 7 2846, and, also,
181565 -     traceability to original sources, reviewed on 950721. ref SDS 7
181566 -     1740
181567 -
181569 -  ..
181570 - Technology Needs Leadership to Overcome Fear of Accountability
181571 -
181572 - Andy Grove reports in his book, "Only the Paranoid Survive," that good
181573 - analysis, for useful "intelligence," see POIMS, ref OF 1 0582, is not
181574 - easy and it is not fun, reported on 980307. ref SDS 12 3101  On 951026
181575 - industry consultant reports ISO requirements for continual learning
181576 - and traceability to original sources are not performed by anyone
181577 - because people do not have enough time. ref SDS 8 3245  This is
181578 - supported by report on 990625 that doctors do not have time to perform
181579 - policy on capturing the record. ref SDS 16 1978
181580 -
181581 -      [On 000225 Eric relates the camel's nose analysis; does not
181582 -      address fear of accountability, etc. ref SDS 34 0784]
181584 -  ..
181585 - The Colloquium's plan to make this work faster, by using technology,
181586 - may may make it easier, and possibly somewhat fun, particularly if
181587 - self-interest dynamics can be incorporated into the DKR design, as set
181588 - out in POIMS. ref OF 1 7117
181590 -  ..
181591 - On 980405 fear of accountability suppresses "intelligence collection"
181592 - activity. ref SDS 13 5065
181594 -  ..
181595 - On 991014 fear of responsibility also impedes collecting useful
181596 - "intelligence."
181598 -  ..
181599 - This record suggests that technology alone is inadequate, set out in
181600 - the New World Order... paper. ref OF 2 4305   A stronger partnership
181601 - is needed between leadership and technology.  This takes leadership
181602 - with a broader vision. ibid. ref OF 2 5653
181604 -  ..
181605 - Eric suggests Jon's objectives to automate Robert's Rules of Order may
181606 - be a "2nd order" effort, built on top of an initial DKR.  He also
181607 - considers advancing priority to co-evolve the systems. ref DRT 1 3233
181609 -     ..
181610 -    Technical references for Roberts Rules of Order...
181611 -
181612 -      • Proposal
181613 -
181614 -
181615 -        http://metalab.unc.edu/bosak/pa/pa.htm
181616 -
181618 -         ..
181619 -      • Preliminary Plan of Action
181620 -
181622 -         ..
181623 -        http://metalab.unc.edu/bosak/pa/pa-act.htm
181624 -
181625 -
181626 -    ...were evidently presented by Jon at the Colloquium. ref DRT 1 4900
181627 -
181629 -     ..
181630 -    Everybody Does It
181631 -    Wide Use of RRO Support Viability of Automated System with DKR
181632 -
181633 -    Robert's Rules has been used for 400 years, with good minds
181634 -    wrestling down the "corner cases" all the way.  It is a codified,
181635 -    documented procedure, which makes automation a straightforward task
181636 -    (unlike an ad hoc procedure). ref DRT 1 2400
181638 -     ..
181639 -    Governments, standards bodies, clubs, board meetings, shareholder
181640 -    meetings, etc., use Robert's Rules of Order.  Wide use provides
181641 -    significant opportunity to improve productivity using proposed
181642 -    DKR technology. ref DRT 1 7820
181643 -
181645 -        ..
181646 -       Everybody Fears Accountability, Knowledge Management Dilemma
181647 -
181648 -       Mere use of Robert's Rules of Order, even with automated tools,
181649 -       does not overcome fear of accountability and responsibility,
181650 -       cited above, ref SDS 0 3564, within the meaning of the legend of
181651 -       Prometheus, reviewed on 991108. ref SDS 17 5810
181652 -
181653 -          [On 000225 Eric relates the camel's nose analysis; does not
181654 -          address fear of accountability, etc. ref SDS 34 0784]
181656 -           ..
181657 -          [On 010114 deliberately managed conversation proposed to
181658 -          accoplish KM. ref SDS 45 1550
181660 -        ..
181661 -       Broadcasts of congressional hearings show well, both the value
181662 -       of good records, and fear that suppresses capturing a good
181663 -       record, that otherwise helps ensure effective decisions.
181664 -
181666 -           ..
181667 -          Cultural Differences Impede Using Robert's Rules of Order
181668 -
181669 -          Eric cites Dave Crocker having mentioned that Robert's Rules
181670 -          would not be effective in many cultures.  Cultural bias
181671 -          requires consideration implementing DKR capabilities.
181672 -          ref DRT 1 2464
181674 -           ..
181675 -          Eric further cites remarks by Jon at the Colloquium
181676 -          explaining the core dilemma of community life...
181677 -
181678 -                "How do we go about making a decision in tough cases,
181679 -                where people are going to disagree even if they have
181680 -                all the facts at their disposal?" (He gave abortion as
181681 -                a well-known example.), ref DRT 1 5632
181682 -
181684 -           ..
181685 -          Standards Imply Bias
181686 -          Conflict Reduced by Fair Process, Consistent Standards
181687 -
181688 -          Standards, units of measure, language, or the XML vocabulary
181689 -          for KM proposed as deliverable by the Colloquium, see below,
181690 -          ref SDS 0 0867, facilitate collaboration to benefit
181691 -          individuals and communities. Adopting any convention voices
181692 -          bias, since comprises have to be accepted that settle on
181693 -          common modes of doing things. Use of English for air traffic
181694 -          control is an example.  Therefore, bias, per se is not the
181695 -          controlling factor.
181696 -
181697 -
181698 -
181699 -
181700 -
1818 -

SUBJECTS
XML Data Format
Vocabulary Standards (XML)
XML Standards Knowledge Repository
OASIS XML Standards Organization

2506 -
250701 -     ..
250702 -    OASIS - XML Vocabulary Standards
250703 -    Organization for Advancement of Structured Information Standards
250704 -
250705 -    OASIS started out doing document-definition standards using SGML,
250706 -    and now plays a major role in defining and archiving XML
250707 -    "vocabulary" standards -- the definition of XML structures you can
250708 -    use for specific purposes. ref DRT 1 8856
250710 -     ..
250711 -    XML standards have been promulgated for...
250712 -
250713 -        math equations
250714 -
250715 -        vector graphics
250716 -
250717 -        business-to-business (B2B) ordering of office supplies
250718 -
250720 -     ..
250721 -    DKR Deliverable - XML Standards Knowledge Management
250722 -
250723 -    Eric suggests the OASIS experience, related above, ref SDS 0 8955,
250724 -    shows the Colloquium deliverable might be *XML-standard* for a
250725 -    knowledge repository, rather than a product to support KM.
250726 -    ref DRT 1 4275
250727 -
250728 -       On 990427 Roy Roebuck proposed deliverable of NSF project was
250729 -       standards for knowledge management. ref SDS 15 9522
250731 -        ..
250732 -       [On 001011 submitted research project to SRI. ref SDS 41 5G5N
250734 -     ..
250735 -    Eric cited Doug Engelbart's observation that standardized knowledge
250736 -    containers and mechanisms for using them enable systems to interact
250737 -    with each other!
250739 -     ..
250740 -    XML supports archiving, accessing, and transmitting information in
250741 -    an Open HyperDocument System or DKR.  Therefore, a standard
250742 -    XML-based vocabulary is needed. ref DRT 1 5670
250743 -
250744 -        [On 00305 Xanadu is presented as an improvement to solve
250745 -        limitations of XML. ref SDS 35 7834]
250746 -
250748 -     ..
250749 -    Robert's Rules of Order Supported by OASIS Standards
250750 -
250751 -    Eric advises that OASIS uses the Robert's Rules procedures.
250752 -
250753 -    He says that augmenting their process means improving the process
250754 -    that defines the standards needed for the Colloquium's knowledge
250755 -    management project, i.e., a DKR. ref DRT 1 8064
250756 -
250757 -
250758 -
250759 -
2508 -

SUBJECTS
Robert's Rules of Order Planning, 000217

2703 -
270401 -     ..
270402 -    Plan for Automating Robert's Rules of Order
270403 -
270404 -    Eric explains a planning to accomplish objective for automating
270405 -    Robert's Rules of Order, ref DRT 1 3400,
270406 -
270407 -    a.  Define working draft of a vocabulary
270409 -         ..
270410 -    b.  Build prototype system to work with it
270412 -         ..
270413 -    c.  Based on the experience we gain from the prototype, revise
270414 -        vocabulary
270416 -         ..
270417 -    d.  Put vocabulary into the hands of OASIS to move towards making
270418 -        it a standard.
270420 -         ..
270421 -    e.  Revise the prototype to use the new structures and "do a
270422 -        Mozilla" -- releasing to the world at large as free DKR
270423 -        browser/authoring tool.
270424 -
270425 -            [On 001101 Mozilla is Netscape v 5, and is cited as an
270426 -            example of failure using Open Source project development.
270427 -            ref SDS 42 4O5K
270429 -         ..
270430 -    f.  The standard and a usable reference implementation leads to
270431 -        large scale emulation -- clients and servers are built, and
270432 -        compete for user's favor -- all of which "educates the market",
270433 -        which creates the market, in reality.
270434 -
270435 -
270436 -
270437 -
2705 -

SUBJECTS
Parliamentary Procedures Automate
Robert's Rules of Order, Automate, 000217

3104 -
310501 -     ..
310502 -    Who Can Do It If Colloquium Automates Process?
310503 -    Parliamentary Assistant Requirements
310504 -
310505 -    Jon proposed a "Parliamentary Assistant" that...
310506 -
310507 -    a.  shows all of the options at any point in the process, and
310508 -        explains them
310510 -         ..
310511 -        A form at each stage presents with *all* the available options,
310512 -        and *only* the available options. ref DRT 1 2520
310514 -         ..
310515 -    b.  The server keeps track of the parliament's state --
310516 -
310517 -        1.  are we voting on a motion?,
310518 -
310519 -        2.  carrying on a debate?, etc.
310521 -     ..
310522 -    Alternatively, the help system could be "Parliamentary Assistant"
310523 -    and underlying server-operations could be the "Parliamentary
310524 -    Floor". ref DRT 1 2457
310526 -     ..
310527 -    Advantages of design...
310528 -
310529 -    a.  Automating the process allows people to take part across time
310530 -        and space. People in physically remote locations can take part
310531 -        in the process without having to be physically present.
310532 -        ref DRT 1 3555
310534 -         ..
310535 -        Don't people do this already with letters, telephone, email?
310536 -        This sounds like the Colloquium.
310538 -         ..
310539 -    b.  Debate could take place, with arguments recorded. Voting could
310540 -        take place over a 48-hour period, giving people time to review
310541 -        the discussions. (Hence the need for a DKR.) That way, we don't
310542 -        all have to be free at the same time to participate in the
310543 -        process. ref DRT 1 2508
310545 -         ..
310546 -    c.  Reduced cost because technology is becoming cheaper and more
310547 -        accessible.  The time and cost of transportation, and schedule
310548 -        conflicts make it difficult to attend meetings. ref DRT 1 1568
310550 -         ..
310551 -        Telephones, mail, television, the Internet all help people
310552 -        communicate without physically meeting.
310554 -         ..
310555 -    d.  Legislators could "work from home", which might have the highly
310556 -        beneficial impact of keeping them in touch with their
310557 -        constituency, rather than becoming part of isolated "power
310558 -        elite" in Washington. ref DRT 1 4484
310559 -
310560 -           On 991217 the Knowledge Management Consortium, International
310561 -           (KMCI) San Francisco chapter sponsored an event that related
310562 -           advantages of co-location for collaboration. ref SDS 18
310563 -           9540
310565 -         ..
310566 -    e.  Some the more onerous (monotonously incessant) duties of the
310567 -        chair would be reduced. ref DRT 1 9379
310568 -
310569 -    f.  "Point of order" would be eliminated because an invalid option
310570 -        would not be presented.  Due to latency, a screen that has not
310571 -        been updated in response to someone's move, might cause a user
310572 -        to make an invalid action, but the system would reject it --
310573 -        and update the screen. ref DRT 1 2520
310574 -
310575 -    g.  "Yielding the floor" or things like that, would be eliminated,
310576 -        easing the work for the Chair, because there is no floor to
310577 -        yield. (On the other hand, might you wind up with multiple
310578 -        things going on simultaneously, and would that be better or
310579 -        worse than the more "serialized" form that occurs in a meeting,
310580 -        where one thing happens at a time?), ref DRT 1 0232
310581 -
310582 -           The tension between serial and parallel processing between
310583 -           the subconscious and conscious span of attention is set out
310584 -           in POIMS. ref OF 1 8774
310585 -
310587 -  ..
310588 - Parliamentary Sessions Resolve Conflicts - Automate
310589 - Impasse, Conflict Resolution through Parliamentary Session
310590 -
310591 - When an impasse occurs using gIBIS for a project to develop an open
310592 - source knowledge management capability, explained below, ref SDS 0
310593 - 0741, one possible solution is to move the decision process to a
310594 - Parliamentary Session. ref DRT 1 0800
310596 -  ..
310597 - To augment decision-making processes going on in the world, then, it
310598 - may make sense to automate parliamentary processes. Then, too, as Jon
310599 - pointed out after the session, you can always adjust the system to set
310600 - the standard you want. You can define a "majority" as 50%, 75%,
310601 - all-but-one, X% in favor and no more than Y% against. ref DRT 1 3850
310602 -
310604 -     ..
310605 -    Inaction Permits Additional Experience to Guide Decisions
310606 -
310607 -    Eric relates Java-inventor James Gosling policy to Do Nothing!!
310608 -    when consensus is not reached, on the grounds that when bright
310609 -    minds cannot agree on the right thing to do, maybe the problem is
310610 -    too murky to make a decision! Rather than making the *wrong*
310611 -    choice, and saddling people with an unattractive design, it was
310612 -    better to leave that feature out of the design until the waters
310613 -    clarified (if ever). ref DRT 1 2499
310615 -  ..
310616 - On 00129 Eric related that Grzegorz Skorupa developed Java-based XML,
310617 - so evidently this is an implementation of Java developed by Gosling,
310618 - noted here today. ref SDS 24 2Y7H
310620 -  ..
310621 - Eric's letter continues...
310622 -
310623 -    An example is W3C standard for XML schemas. Apparently many people
310624 -    feel that it has become rather huge and complex (much like SGML).
310625 -    It may have resulted from the politics of "satisfying everyone" --
310626 -    of not disagreeing with anyone else's proposal so that your own
310627 -    would be accepted. ref DRT 1 1061
310629 -     ..
310630 -    Bill Smith is reported to have commented, when XML was presented,
310631 -    complaints were made by many people over a 3 hour period that
310632 -    needed features were omitted from the standard; but, no two people
310633 -    ever named the same feature!  It seemed that all the features left
310634 -    out were really idiosyncratic ones -- not core features that
310635 -    everyone needed. He said he knew then that they were on the right
310636 -    track! ref DRT 1 5472
310638 -     ..
310639 -    That experience, along with the general "design by committee"
310640 -    scenario, seems to imply that IBIS-style procedures might well be
310641 -    sufficient for automating open source design efforts. In those
310642 -    cases where consensus cannot be reached, perhaps no decision at all
310643 -    is the wisest course! ref DRT 1 4071
310645 -     ..
310646 -    Doing nothing is a "decision". Failing to make difficult decisions
310647 -    is not always effective. ref DRT 1 4075
310649 -     ..
310650 -    To augment many of the decision-making processes that are currently
310651 -    going on in the world, then, it may make sense to automate
310652 -    parliamentary processes. Then, too, as Jon pointed out after the
310653 -    session, you can always adjust the system to set the standard you
310654 -    want. You can define a "majority" as 50%, 75%, all-but-one, X% in
310655 -    favor and no more than Y% against. ref DRT 1 3850
310656 -
310657 -
310658 -
310659 -
310660 -
310661 -
3107 -

SUBJECTS
Law Trial Case Organization
Law Metric of Conformance to Accepted Agreed Conduct
Law Intelligence for Management
Law is Microscope of Discovery for Truth, Causation
Legal Metrics Discover Mistakes

3707 -
370801 -  ..
370802 - Judicial Model of Decision Applies Experiential Record and Standards
370803 -
370804 - Eric cites as an alternative posed by a retired lawyer during
370805 - Colloquium #7, to use the Judicial model (adjudicative) where a body
370806 - of knowledge is built up over time, rather than going for a "decision"
370807 - all at once, and notes a DKR can support this process. ref DRT 1 4292
370808 -
370809 -     Judicial process is explained in the NWO... ref OF 2 2536
370811 -      ..
370812 -     Concurrent Discovery uses technology to advance legal process of
370813 -     aligning the work to avoid disputes, reported on 960620.
370814 -     ref SDS 9 1101
370816 -      ..
370817 -     It is not clear that Robert's Rules of Order conflicts with the
370818 -     judicial model of drawing on past experience for making decisions.
370819 -     Robert's Rules manage contributions from participants, all of whom
370820 -     typically are relying on their experience.  In court, the judge
370821 -     and procedure guide presentation of information, based on the
370822 -     experience of witnesses.
370824 -  ..
370825 - Eric indicates a "judicial"-style DKR is appropriate for an individual
370826 - engaged in doing a design. That DKR might contain all the information
370827 - you digested as a student, and all the design experience you acquired
370828 - since then on the job. As you think about how the system should be
370829 - implemented, you may well consult your DKR for ideas, alternatives,
370830 - and suggestions. ref DRT 1 1290
370831 -
370832 -      This explanation seems to draw on an experiential base, also,
370833 -      designated as necessary for the Robert's Rules of Order system,
370834 -      per above. ref SDS 0 1092
370835 -
370836 -
370837 -
370838 -
3709 -

SUBJECTS
Collaboration Helps Everyone

3803 -
380401 -  ..
380402 - Collaboration Supported by DKR Technology
380403 -
380404 - Eric develops the notion of individual and "project" or possibly
380405 - "community," experience, that is accumulated, and shared through
380406 - collaboration, as called out above for automating Robert's Rules of
380407 - Order, ref SDS 0 1092, which is a objective of the Colloquium, apart
380408 - from the decision model used. ref DRT 1 2279
380410 -  ..
380411 - He suggests others interacting with the repository might save that
380412 - information as part of their personal DKR. Some parts they might
380413 - choose to ignore, as outside their area of expertise, superfluous, or
380414 - redundant with previously stored material. But the useful parts would
380415 - become part of the compact DKR they carry forward in life. ref DRT 1
380416 - 1054
380417 -
380418 -     This reflects the POIMS design of integrating personal and
380419 -     organizational management. ref OF 1 1054 and ref OF 1 7117
380421 -  ..
380422 - Eric describes a system goal of education might be to add material to
380423 - a student's DKR -- material they understand and can access when
380424 - needed. As ideas and knowledge migrate from repository to repository,
380425 - human knowledge spreads. That may be the fundamental idea of "idea as
380426 - virus" in books like (or based on) Richard Dawkins' "The Selfish
380427 - Gene". ref DRT 1 2254
380428 -
380429 -
380430 -
380431 -
380432 -
380433 -
380434 -
3805 -

SUBJECTS
gIBIS Decision Modeling
Revise Endorsements, 000218
Forms Limit Options Guide Discussion for Decision, 000218
IBIS Rigid Ineffective, 000218
Authority to Decide Required for IBIS, Open Source Has No Authority,
Rigid Ineffective for Decision, 000220
IBIS Rigid Organization Hampers Productivity KM Dilemma
IBIS Rigid Application Limit Usefulness, Eric Armstrong
IBIS Too Rigid Flexible Structure Needed for Intelligence,

4911 -
491201 -  ..
491202 - IBIS Decision Modeling Supports Acclimation Process
491203 -
491204 - Follow up ref SDS 27 9282.
491205 -
491206 - Eric indicates that IBIS was explained by Jon Bosak in a presentation
491207 - to the Colloquium at Stanford, ref SDS 0 0873, as a decision-making
491208 - model which offers a different approach from using automated Robert's
491209 - Rules of Order based on the Parliamentary Assistant, also, explained
491210 - above, ref SDS 0 9674, for two (2) cases...
491212 -  ..
491213 - On 000212 gIBIS was proposed to support reasoning based on the record.
491214 - ref SDS 27 9282  On 000130 Eric considered gIBIS for organizing
491215 - communications among the Colloquium contributors. ref SDS 25 0866
491216 - IBIS and gIBIS was first reviewed in the record on 940527. ref SDS 6
491217 - 0783
491218 -
491219 -     1.  Autocratic decisions where everyone presents their proposal
491220 -         and supporting evidence, and then the "supreme ruler" makes a
491221 -         decision. ref DRT 1 4902
491223 -          ..
491224 -         He says an automated model can record alternatives and the
491225 -         arguments so they can be re-examined when needed, ref DRT 1
491226 -         2840, per explanation for RRO. ref SDS 0 0873
491228 -          ..
491229 -         Eric comments this system needs authority to make decisions.
491230 -         It is possible to reach agreement in a meeting of equals,
491231 -         though, in one case:
491233 -          ..
491234 -     2.  When a decision is reached by "acclamation".
491235 -
491236 -         For decisions involving two alternatives, three people may
491237 -         endorse #1, and 2 people endorse #2. After reflection, perhaps
491238 -         one person changes to endorse #1. Then the last person decides
491239 -         to "go along with the group", and endorses #1, as well. The
491240 -         voting is now unanimous, and a decision has been reached.
491241 -         ref DRT 1 1428
491242 -
491244 -  ..
491245 - IBIS implementation requires ability to "change" an endorsement.
491246 -
491247 - The original endorsement should probably remain on record, but link to
491248 - the new one. Making the change should either require an explicit
491249 - "change endorsement" action or, if accomplished by the simple act of
491250 - endorsing a different alternative, the system should verify that you
491251 - want to change your endorsement. (You may have forgotten that you
491252 - endorsed a different proposal earlier and may need to review your
491253 - original reasons. When the system looks for endorsements, it should
491254 - ignore any with a non-null link. ref DRT 1 3008
491255 -
491256 -
491258 -  ..
491259 - IBIS and DKR Higher Priority than Alternative DKR and RRO
491260 -
491261 - Eric suggests that it may be possible to co-evolve a parliamentary
491262 - augmenter with a DKR. If not, it would seem that the a DKR / OHS /
491263 - IBIS system for Open Source Development would have higher precedence.
491264 - ref DRT 1 0540
491265 -
491267 -  ..
491268 - IBIS Rigid Rules Limit Acceptance
491269 - Forms in gIBIS Aid Discussion with Logically Limited Options
491270 -
491271 - In his letter on 000217, Eric relates discussion by Jon Bosak during
491272 - Colloquium #7 that forms are used to guide participants through a
491273 - Parliamentary Process.  Eric says this brought to mind a related issue
491274 - with IBIS, per above. ref SDS 0 0741  A system that "limits options"
491275 - for a response according to context would help in an IBIS-style
491276 - discussion, as well. ref DRT 1 4422
491278 -  ..
491279 - For example, in IBIS you never make a proposal without first asking a
491280 - question -- that identifies the problem you are trying to solve and
491281 - keeps the design space open by providing a place to hang other
491282 - alternatives. ref DRT 1 2695
491284 -  ..
491285 - See further analysis. ref DRT 1 4148
491287 -  ..
491288 - Rigidly logical rules are useful, but discourage acceptance
491289 - ref DRT 1 4260
491291 -  ..
491292 - Rigid rules for organization are resisted because they take a lot of
491293 - time to apply when the complexity of communication reaches the level
491294 - people can readily manage issues carefully.  Peter Drucker explains
491295 - people have given up because communication is too complex, reported on
491296 - 931130. ref SDS 5 3851  On 990303 George Miller's research in
491297 - cognitive science indicates people can only manage about seven (7)
491298 - subjects and then to lose track and forced to rely on remembering only
491299 - the gist of information; understanding fails, causing frustration,
491300 - anger, error, loss and conflict. ref SDS 14 5328   Jeremy Campbell
491301 - says people pay a price for relying on the gist of information,
491302 - reviewed ten (10) years earlier on 900303. ref SDS 2 7Z6G  On 971008
491303 - USACE reported limited span of attention that makes communication
491304 - methods difficult for rigid methods overlooks most issues that arise
491305 - in daily work, causing continual bumbling that requires rework, extra
491306 - cost, delay, conflict, crisis and calamity. ref SDS 11 1273
491308 -  ..
491309 - POIMS calls for flexibility to provide common structure naturally, and
491310 - additional structure can be used if time and circumstances warrant,
491311 - ref OF 1 M17I, based on analysis on 890523. ref SDS 1 P13O
491312 -
491313 -         [On 001008 Eric Armstrong explains that when too many subjects
491314 -         are tracked with dialog maps, the complexity becomes
491315 -         overwhelming. ref SDS 40 N38W
491317 -          ..
491318 -         [On 010914 Eric Armstrong provides analysis of limitations
491319 -         using graphical mapping. ref SDS 47 UU8N
491321 -          ..
491322 -         [On 030317 Jeff Conklin comments on challenge of applying IBIS
491323 -         to complex communication, and explains use of dialog maps in
491324 -         meetings to help people follow complex issues. ref SDS 49 IK5N
491326 -      ..
491327 -     On 940527 IBIS and gIBIS were first reviewed as applications which
491328 -     support the SDS design as described in POIMS. ref SDS 6 0783
491330 -      ..
491331 -     Time required to use IBIS is related to the problem of cognitive
491332 -     overhead that limits acceptance. ref SDS 6 F95N
491334 -  ..
491335 - A paper was evidently presented at the Colloquium that describes some
491336 - difficulties people have using IBIS, which further reflects the
491337 - challenge of integrating flexibility and structure of forms, explained
491338 - in POIMS. ref OF 1 0561
491339 -
491340 -
491341 -       http://web.uvic.ca/~ckeep/hfl0104.html
491343 -  ..
491344 - Eric suggests IBIS can be a hierarchy that builds on top of a
491345 - free-wheeling email discussion, by creating tagged nodes that point to
491346 - elements from that discussion.  Keeping the labels separate from the
491347 - messages might provide the best of both worlds, and make it possible
491348 - to make new versions of the IBIS summary without affecting the
491349 - underlying discussion at all.
491350 -
491351 -      SDS design integrates hierarchial and relational structure, noted
491352 -      by Morris on 910810. ref SDS 3 7793
491354 -       ..
491355 -      POIMS explains requirement for balancing speed and structure
491356 -      which in turn requires a flexible structure, otherwise no
491357 -      organizational memory will get generated, and no benefit will
491358 -      occur. ref OF 1 M17I
491360 -     ..
491361 -    [...later today Dick Karpinski proposes gIBIS as part of SDS.
491362 -    ref SDS 31 4345
491364 -     ..
491365 -    [On 000220 Eric submits Reference Materials that list sources from
491366 -    Colloquium contributors. ref SDS 32 6480]
491368 -     ..
491369 -    [On 000223 Eric cites IBIS helpful to organize and locate
491370 -    information. ref SDS 33 4722
491372 -     ..
491373 -    [On 000505 IBIS incorporated into OHS requirements. ref SDS 36 2650
491375 -     ..
491376 -    [On 000602 Jack Park supports IBIS requirements for OHS.
491377 -    ref SDS 37 6720
491379 -     ..
491380 -    [On 000614 IBIS proposed to support Wiki. ref SDS 38 4939
491382 -     ..
491383 -    [On 000716 Joe Ransdell cautions about distinction between formal
491384 -    logic and practical reasoning. ref SDS 39 2200
491386 -     ..
491387 -    [On 001130 Jack Park reports the SDS design supports the structure
491388 -    for knowledge management and the SDS interface makes the structure
491389 -    of knowledge useful to people. ref SDS 43 H17O
491391 -     ..
491392 -    [On 001130 Jack Park proposes adding IBIS capability to SDS.
491393 -    ref SDS 43 AZ7J
491395 -     ..
491396 -    [On 001220 Gary Johnson submits evidence indicating rigid
491397 -    structure, like IBIS, reduce productivity. ref SDS 44 RD9N
491399 -     ..
491400 -    [On 010114 John Maloney proposes deliberately managed conversation
491401 -    to accomplish KM. ref SDS 45 1550
491403 -     ..
491404 -    [On 010426 Jeff Conklin who promoted IBIS in 1996 has withdrawn
491405 -    support for "automated IBIS" systems contemplated by the OHS/DKR
491406 -    effort, according to Eric Armstrong. ref SDS 46 RN4H
491408 -     ..
491409 -    [On 030207 John Deneen relates a discussion lead by Eric Armstrong
491410 -    using IBIS encountered difficulties. ref SDS 48 033O
491411 -
491412 -
491413 -
491414 -
491415 -
491416 -
491417 -
491418 -
491419 -
4915 -

SUBJECTS
Invisible Links, 000218
Editing Core Capability
Implicit Hyperlinks

5505 -
550601 -  ..
550602 - Implicit Links, Multi-links, Mouseover
550603 -
550604 - Bill Bearden's letter explains a User Interface (UI) issue.  HTML,
550605 - only supports one-way, one-thing links. XML supports links between a
550606 - word in our data (could be a document) and many other things
550607 - (multi-way, multi-thing). This means we can no longer expect the
550608 - simple single-click to take us where we want to go. ref DRT 3 0816
550610 -  ..
550611 - Bill suggests using "mouseover" UI to expose links. When the user
550612 - rests the mouse pointer on a word, they will see a list of links from
550613 - which to choose. Perhaps the first thing they see in the list is not a
550614 - link at all, but a contextual definition of the word (or phrase) if
550615 - one exists. ref DRT 3 7200
550616 -
550617 -
550619 -  ..
550620 - Invisible Links in XML Editor
550621 -
550622 - Follow up ref SDS 24 3383.
550623 -
550624 - A second letter, ref DRT 2 0001, from Eric seems to compliment Bill
550625 - Bearden's letter, and concur with an earlier letter from Henry van
550626 - Eyken proposing that the editor support invisible links.
550628 -  ..
550629 - Henry says a secondary form of hyperlink is helpful for obtaining the
550630 - meaning of abbreviations and specialized terms.  These links would not
550631 - be underlined nor highlighted. A reader would simply expect that
550632 - clicking on them would immediately generate the appropriate
550633 - definition, preferably in a separate window so as not to interrupt the
550634 - primary document being read.
550636 -  ..
550637 - Eric advises that XML support normal and invisible links. ref DRT 2
550638 - 1564
550640 -  ..
550641 - He seems to suggest the invisible link feature would be helpful for
550642 - language interpretation, as for example where English is used for
550643 - international communication.  This capability would help peoople for
550644 - whom English is not the native language. ref DRT 2 2655
550646 -  ..
550647 - Eric sets out some requirements. ref DRT 2 2537
550648 -
550649 -
550650 -
550651 -
550652 -
550653 -
550654 -
550655 -
550656 -
550657 -
550658 -
5507 -