CONTACTS 
0201 - Bootstrap Institute
020101 - Mr. Douglas C. Engelbart, Ph.D.

SUBJECTS
OHS/DKR Meeting at SRI 000427

0403 -
0403 -    ..
0404 - Summary/Objective
0405 -
040501 - Follow up ref SDS 71 0000, ref SDS 66 0000.
040502 -
040503 - Did not attend the meeting.  Received accounts from people who did
040504 - attend.
040505 -
040506 -    [On 000428 received letter from Eric Armstrong. ref SDS 78 0001
040507 -
040508 -
040509 -
040510 -
040511 -
040512 -
0406 -

SUBJECTS
Staff

0503 -
0504 - Discussion
050501 -  ..
050502 - Introductions - Diverse Skills Focused on DKR Project
050503 -
050504 - Follow up ref SDS 71 2079, ref SDS 66 2079.
050505 -
050506 - No report of new attendees.
050507 -
050508 -
050509 -
050510 -
050511 -
0506 -

SUBJECTS
Sponsor/Stakeholder Planning
Killer Application
Existing Capability, Start with What is Available, 000302
Pilot Test New Capabilities, 000227
Zope Email System, 000427
SlashDot Email System, 000427
ArsDigita Email System, 000427
Document Management Pilot Test New Capabilities, 000227
Pilot Test Email for Organizing and Thought Tracking, 000428
Webmail Adds Content SDS Makes Internet and Web Useful for Daily Mana
Weblogs Email on Internet Similar to Webmail Journaling

2713 -
271401 -  ..
271402 - Search for "Killer App" Focuses on Knowledge/Enterprise Management
271403 - Sponsors Looking for Projects in Knowledge Management Arena
271404 -
271405 - Follow up ref SDS 71 4877, ref SDS 66 4877.
271406 -
271407 -    At the end of the meeting on 000413 Eric seemed to indicate plans
271408 -    to consider sponsor outreach and planning for funding at the
271409 -    meeting today, perhaps including results of Doug's meeting with SRI
271410 -    and a major potential sponsor on Monday, 000410, ref SDS 66 4877,
271411 -    which was reported on 000419 to be moved to 000425.
271413 -     ..
271414 -    This task was evidently not done today.
271415 -
271417 -     ..
271418 -    Email Improved by WebLog tools: SlashDot, Zope, ArsDigita
271419 -    Starter Tools for DKR Email, Project Team to Pilot Test
271420 -    Pilot Test Email Programs to Evaluate DKR Starter Technologies
271421 -
271422 -    Follow up ref SDS 70 4877, ref SDS 71 2537.
271423 -
271424 -    On 000420 project team planned to evaluate "starter technologies,"
271425 -    ref SDS 71 5073, by pilot testing tools to replace conventional
271426 -    email, ref SDS 71 2537, based on a list of tools acceptable to the
271427 -    team, submitted by Eric Armstrong in a letter earlier that same
271428 -    day. ref SDS 70 4877  This plan reflected recommendations over the
271429 -    past 4 months to implement bootstrapping methodology to learn by
271430 -    experience, also, cited in the record on 000420. ref SDS 71 6570
271431 -
271432 -         [On 000504 Zope is strong candidate for project discussions.
271433 -         ref SDS 82 3944
271435 -          ..
271436 -         [On 000505 review of project requirements spec v0.6 shows need
271437 -         for team to begin using Zope or similar tools to get a feel
271438 -         for a connected environment. ref SDS 83 2852
271440 -          ..
271441 -         [On 000516 Eugene Kim reports Lee Iverson making progress
271442 -         setting up a Zope/Wiki server for the project. ref SDS 86 4971
271444 -     ..
271445 -    In a separate letter to the project team today, Lee Iverson submits
271446 -    use case methods for open source software projects, warning that
271447 -    developers, like all of us, like to use tools they already know how
271448 -    to use, ref SDS 77 0713, per Andy Grove's report in the record on
271449 -    980307 that executives loathe to change their work practices.
271450 -    ref SDS 13 1657
271451 -
271453 -     ..
271454 -    Weblogs Proposed to Improve Email
271455 -
271456 -    Lee Iverson gave a short report today on starter technologies using
271457 -    the concept of "WebLog" software exemplified by the SlashDot
271458 -    website to improve conventional email, per Eric's letter.
271459 -    ref DRP 15 0001
271461 -     ..
271462 -    This may implement Doug's requirement on 000405 calling for
271463 -    addressability in email, since the web supports HTML, and this
271464 -    enables adding anchors that are addressable. ref SDS 60 2484
271466 -     ..
271467 -    On 971021 SDS was ported to the Internet and enabled webmail for
271468 -    creating and delivering intelligence anytime, anywhere. ref SDS 11
271469 -    3636
271470 -
271471 -        [On 000428 received Eric's letter. ref SDS 78 0001
271472 -
271473 -        [On 000502 Eugene Kim commented that none of the email
271474 -        enhancement programs reviewed by the project team improve upon
271475 -        conventional email. ref SDS 79 0001
271477 -         ..
271478 -        [On 000503 Eric expects Zope SlashDot, etc, can be improved by
271479 -        "hacking." ref SDS 80 3465
271481 -         ..
271482 -        [On 000504 Eugene submitted use case analysis of OHS based on
271483 -        his work developing a DKR.  Jack Park comments favorably on
271484 -        Euegne's proposed scope. ref SDS 81 0784
271486 -         ..
271487 -        [On 000504 SlashDot ruled out. ref SDS 82 5922
271489 -         ..
271490 -        [On 000505 updated project spec v0.5 does not mention "Starter
271491 -        Technologies" under "Starting Points." ref SDS 83 3969
271493 -         ..
271494 -        [On 020301 blogs and klogs sound similar to weblogs that
271495 -        support journaling, lists and outlining. ref SDS A5 GT4M
271497 -         ..
271498 -        [On 020716 customer asks to compare SDS and Blogs. ref SDS A6
271499 -        RV3O
271501 -     ..
271502 -    At the project meeting on 000420, the team liked email that seems
271503 -    fast and easy. ref SDS 71 0784  On 990924 conventional email is
271504 -    stream of conscious reasoning that causes meaning drift, mistakes,
271505 -    loss, conflict due to lack of alignment, ref DIP 1 1045, explained
271506 -    further on 991101, ref SDS 19 0857, which causes false knowledge
271507 -    that makes...
271508 -
271510 -              ..
271511 -             Communication the biggest risk in enterprise!
271512 -
271513 -
271514 -    ...explained in POIMS. ref OF 1 8316  On 000405 Jack Park reported
271515 -    SDS provides stream of conscious work product. ref SDS 59 6305 Bill
271516 -    Beardon noted that SDS provides sophisticated DKR environment.
271517 -    ref SDS 59 3877
271519 -     ..
271520 -    On 000424 Eric noted OHS is not defined, at least to the investor
271521 -    market; evidently improving email is a fundable market. ref SDS 76
271522 -    5880
271524 -     ..
271525 -    Lee advised that SlashDot was difficult to install, but works well.
271526 -
271527 -        [On 000504 SlashDot ruled out. ref SDS 82 5922
271529 -     ..
271530 -    Lee feels WebLog would provide a much better way to track our
271531 -    thoughts than an email archive -- with the added benefit that we
271532 -    might choose to extend the system we install, or at the very least
271533 -    reuse the information stored in the database repository, rather
271534 -    than having it sit in a virtually inaccessible email archive.
271535 -    (SlashDot allows for adding comments, evaluating comments, and
271536 -    evaluating the evaluators --which affects the weighting of their
271537 -    evaluations.), ref DRP 15 1008
271538 -
271539 -        On 000120 the challenge of generating and applying information
271540 -        connected into useful knowledge presents a burden, like opening
271541 -        Pandora's Box. ref SDS 23 2345
271543 -         ..
271544 -        On 000405 Jack Park asked if SDS environment that connects
271545 -        information over time, would be useful? ref SDS 59 2928
271546 -        ..
271547 -        On 000420 report that Crit team uses regular email rather
271548 -        than connecting information into knowledge. ref SDS 71 4911
271550 -     ..
271551 -    Project team proposed to evaluate other starter technologies for
271552 -    enhancing email, per Eric's letter. ref DRP 16 0001
271553 -
271554 -        [On 000428 received Eric's letter. ref SDS 78 5933
271555 -
271556 -        [On 000525 assignments to evaluate starter technologies were
271557 -        made during project meeting at SRI. ref SDS 90 4084
271559 -     ..
271560 -    Lee identified 4 possible candidates for our use, ref DRP 15 4473,
271561 -    most of which also came highly recommended by Paul Fernhout in an
271562 -    earlier message, see for example on 000422 Paul cites the Zope
271563 -    business model. ref SDS 74 5933
271564 -
271565 -      •  SlashDot (Apache, Perl, MySQL)
271567 -            ..
271568 -           [On 000504 SlashDot ruled out. ref SDS 82 5922
271570 -          ..
271571 -      •  PHP/SlashDot (Apache, PHP, MySQL)
271572 -
271573 -           [On 000504 PHP/SlashDot ruled out. ref SDS 82 5922
271575 -          ..
271576 -      •  Zope (Python, MySQL)
271577 -
271578 -           [On 000428 Eric Armstrong comments on evaluation criteria
271579 -           for Slashdot and Zope. ref SDS 78 6Y3M
271581 -          ..
271582 -      •  ArsDigita (Tcl, AolServer, Oracle)
271583 -
271584 -           [On 000504 ArsDigita ruled out. ref SDS 82 5922
271586 -         ..
271587 -        [On 000428 initially favors PHP/SlashDot and Zope because they
271588 -        have the most modular architecture and the most reasonable
271589 -        language for hacking. ref SDS 78 4425
271591 -         ..
271592 -        [On 000502 Eugene Kim commented that none of the email
271593 -        enhancement programs reviewed by the project team improve upon
271594 -        conventional email. ref SDS 79 0001
271596 -         ..
271597 -        [On 000503 Eric expects Zope SlashDot, etc, can be improved by
271598 -        "hacking." ref SDS 80 3465
271600 -         ..
271601 -        [On 000504 Zope and JavaCorporate Suite will be pursued to
271602 -        enhance project email for collaboration. ref SDS 82 3944
271603 -
271605 -     ..
271606 -    Wiki-Style Collaborative Document Management
271607 -
271608 -    One of these systems includes a Wiki-style collaborative document
271609 -    system.  Another possibility is to use WikiS (the Squeak-based
271610 -    version) in conjunction with a WebLog, to get the best possible
271611 -    combination of threaded discussions and documents that summarize
271612 -    them. ref DRP 15 2709
271613 -
271614 -       [On 000504 Zope supports Wiki. ref SDS 82 9000
271615 -
271616 -
271617 -
271618 -
271619 -
2717 -

SUBJECTS
Sun Microsystems Donated Server Space
Sponsor Outreach, Support, 000324
Web Site Server Vendor
Engelbart, Doug

3506 -
350701 -  ..
350702 - Server Space for DKR Donated by Sun Microsystems
350703 -
350704 - Follow up ref SDS 71 5962.
350705 -
350706 - No report of progress using server donated by Sun, per Eric's letter
350707 - on 00042, ref SDS 72 0001
350708 -
350709 -
350710 -
350711 -
350712 -
3508 -

SUBJECTS
Property Rights in Knowledge Organization
Commercial Viability
Ownership Investment Risk
Development Investment Risk

4006 -
400701 -  ..
400702 - Legal Issues Arising from Open Source and Sponsor Support
400703 -
400704 - Follow up ref SDS 71 3055, ref SDS 66 3055.
400705 -
400706 - There was no discussion on getting a license or other standing
400707 - required to operate, noted at the meeting on 000330, ref SDS 55 3995,
400708 - possibly because decision has been taken for SRI to be organizational
400709 - platform, per meeting on 000420. ref SDS 71 6630
400711 -  ..
400712 - There was no discussion for licensing options discussed on 000324, and
400713 - submission by Eric Armstrong of license ideas on 000421 ref SDS 72
400714 - 3055
400715 -
400716 -
400717 -
400718 -
400719 -
4008 -

SUBJECTS
OHS Open Hyperdocument System
OHS Editor XML, Requirements, Specs
Traction Journal Management, 000326
WBI Transcoding, IBM, 000324
Crit Team Used Email Instead of Knowledge, 000326
Communication Biggest Risk in Enterprise, Dilemma
Engineering Management
Email Degrades Writing, Understanding
Fast and Easy, Fools Gold, Talking, Listening, Pictures
Email Fast, Easy Like Talking, Fools Gold, Unorganized, Unconn
Williams, Joe

5513 -
551401 -  ..
551402 - Project Objective to Produce DKR Capability
551403 -
551404 - Follow up ref SDS 71 2808, ref SDS 66 2808.
551405 -
551407 -     ..
551408 -    Knowledge Management Definition
551409 -
551410 -    Follow up ref SDS 71 5555, ref SDS 66 5555.
551411 -
551412 -    No report on Debra England's suggestion on 000420 for team members
551413 -    to write up the purpose of the project, ref SDS 71 5555, to
551414 -    identify core function of DKR, called out by Eric on 000208.
551415 -    ref SDS 29 8960
551417 -     ..
551418 -    No evident discussion of Eric's submission on 000421, ref SDS 72
551419 -    5933, supplemented on 000423 proposing DKR to augment human
551420 -    intellignece, ref SDS 75 5933; nor of Adam Cheyer's submission
551421 -    on 000424. ref SDS 76 0002
551422 -    ..
551423 -    Discussion above on using email tools, ref SDS 0 5985,
551424 -    reflects Eric's idea to focus on improving email. ref SDS 75 5943
551425 -
551427 -     ..
551428 -    Editor Based on XML Initial Project Deliverable
551429 -    Collaborative Document System and OHS Supported by Editor
551430 -
551431 -    Follow up ref SDS 71 5880, ref SDS 66 5880.
551432 -
551433 -    No record of discussion, but on 000423 Eric proposes in a letter to
551434 -    the team that the purpose of the DKR project which he says is to
551435 -    enhance human intelligence, ref SDS 75 5096, and be accomplished by
551436 -    initially producing an enhanced email program. ref SDS 75 5943
551437 -
551438 -
551440 -     ..
551441 -    Atomic Data Structures Derive from Fundamental Information Unit
551442 -    Fundamental Information Unit Focuses DKR Design Effort
551443 -
551444 -    Follow up ref SDS 71 4004.
551445 -
551446 -    No evident discussion today of Joe Williams comprehensive
551447 -    presentation on 000420 of DKR and OHS framework. ref SDS 71 4004
551449 -     ..
551450 -    No discussion of atomic data structures submitted by Eric on
551451 -    000423. ref SDS 75 4977
551452 -
551453 -
551454 -
5515 -

SUBJECTS
Augment, Doug Engelbart's System at SRI Beginning in 1960s
Augment Human Capabilities
Engelbart, Doug
Iverson, Lee
Augment Presentation, Engelbart, Iverson, Williams, Yee, 000420

6207 -
620801 -     ..
620802 -    Augment Project at SRI in 1960s Sets Design Objectives
620803 -    Demonstration for Augment at Future Project Meeting
620804 -
620805 -    Follow up ref SDS 71 5922.
620806 -
620807 -    Not sure if Augment was presented today, per Eric's letter on
620808 -    000421, ref SDS 72 0001, again on 000423, ref SDS 75 0005, and
620809 -    Jack's report on 000426 that Doug's Augment sets the stage and
620810 -    vision for an effective DKR.
620811 -
620812 -
620813 -
620814 -
620815 -
620816 -
620817 -
6209 -

SUBJECTS
Use Case Method Define Requirement, 00000000
Iverson, Lee
Software Programming Program, Use Case Analysis, 000406

6705 -
670601 -  ..
670602 - Use Case Methods for Software Design
670603 -
670604 - Follow up ref SDS 71 4933, ref SDS 48 6052.
670605 -
670606 - No record of discusion on use case work.
670607 -
670608 -
670609 -
670610 -
6707 -

SUBJECTS
Communication Manager Saves Time So Managers Have Time to Think
CODIAK Intelligence Capabilities
Com Manager Sue Ling Point Out Contradictions Prod, 000427
Feedback Metrics Meeting Notes Improve Productivity Lessons Learned
Procedures Meeting Notes
Meeting Notes Improve Understanding, 000509
Manage Communication Guide to Running Meetings, Doug Engelbart
Guide to Running NICS, Doug Engelbart
NIC Guide to Running Meetings, Doug Engelbart
Professional Role Use SDS Like Pilot Flies Airplane
Education Training Needed for New Professional Role Needed SDS Skills

8313 -
831401 -  ..
831402 - Guide to Running NICs Gathers Intelligence, Provides Feedback
831403 - WBI Transcoding Vector Records Information, Gathers Intelligence
831404 - Communication Manager Proposed to Complement Tools for DKR
831405 -
831406 - Follow up ref SDS 71 3995, ref SDS 66 5148.
831407 -
831408 - Doug presented WBI Transcoding vector, planned on 000420. ref SDS 71
831409 - 8648, per Eric's letter. ref DRP 17 0001
831410 -
831411 -     [On 000428 received Eric's letter. ref SDS 78 0001
831413 -      ..
831414 -     [On 000504 no follow up. ref SDS 82 3995
831416 -      ..
831417 -     [On 000511 Jack Park and Howard Liu explained implementation
831418 -     proposal. ref SDS 85 4674
831420 -      ..
831421 -     [On 001025 Doug submits OHS Launch plan that calls for initial
831422 -     project to develop Hyperscope, which
831423 -     may support WBI transcoding.
831425 -      ..
831426 -     [On 010122 BrowseUp may accomplish some of WBI transcoding
831427 -     capability. ref SDS A4 0001
831428 - ..
831429 - Doug offered a new vision today. ref DRP 17 8282
831431 -  ..
831432 - His model system has always been divided into three components:
831433 -
831434 -    •  Recording dialog
831435 -
831436 -    •  Gathering intelligence
831437 -
831438 -    •  "State of the system" summary, or "handbook".
831440 -  ..
831441 - Along those lines, Doug proposed building a...
831442 -
831443 -
831444 -                   Guide to Running NICs
831445 -
831446 -
831447 - ...to be monitored/edited by Su-Ling Yee.
831448 - ..
831449 - The idea is that we will add information to this knowledge base,
831450 - Su-Ling will look for contradictions and prod contributors, and we
831451 - will grow the knowledge repository's capabilities as we use it.
831452 - ref DRP 17 1170
831453 -
831454 -     [On 001216 Doug willing to answer questions from team on progress
831455 -     of the work. ref SDS A3 0001
831457 -  ..
831458 - On 000227 Eric Armstrong explained advantage of connecting daily
831459 - working information to relevant project history. ref SDS 35 1248
831461 -  ..
831462 - On 000327 Doug pointed out his 1972 paper explaining a Knowledge
831463 - Workshop for handling daily working information. ref SDS 52 3971  This
831464 - seems to have evolved into a process of Dynamic Knowledge Capture in
831465 - Doug's paper, "Technology Template Project," dated 980128, which Eric
831466 - cited on 000614. ref SDS 94 GF9G  Thus, the Guide to Running NICs is
831467 - endemic to creating a DKR.
831468 -
831469 -      [On 000504 no work product submitted for review of progress so
831470 -      far accomplishing this task. ref SDS 82 1575
831472 -       ..
831473 -      [On 000508 Eric reported that forcing himself to write up the
831474 -      record improves his understanding of what needs to be done, and
831475 -      gaps that require clarification. ref SDS 84 5938
831477 -       ..
831478 -      [On 000511 Eugene Kim assigned Project Manager to implement the
831479 -      Guide to Running NICs. ref SDS 85 0784
831481 -       ..
831482 -      [On 000516 Paul Fernhout commended SDS methodology. ref SDS 86
831483 -      0001
831485 -       ..
831486 -      [On 000516 Eugene discloses plans to prepare formal meeting
831487 -      minutes. ref SDS 86 3740
831489 -       ..
831490 -      [On 000517 Eric Armstrong reported during at meeting Intel that
831491 -      the record he prepared on a project in Texas one year was
831492 -      helpful. ref SDS 87 2064
831494 -       ..
831495 -      [On 000518 Howard Liu enters record during meeting. ref SDS 88
831496 -      8160
831498 -       ..
831499 -      [On 000518 "knowledge" defined as experiential record showing
831500 -      alignment with related sources. ref SDS 88 3528
831502 -       ..
831503 -      [On 000524 received Howard's meeting minutes. ref SDS 91 0001
831505 -       ..
831506 -      [On 000613 received good record for meeting on 000601; does not
831507 -      include "intelligence" called out today. ref SDS 93 0001
831509 -       ..
831510 -      [On 000615 Eugene Kim affirmed intent that project "intelligence"
831511 -      requires input from all team contributors. ref SDS 95 4455
831513 -       ..
831514 -      [On 000824 Eric objects to record connected to relevant history
831515 -      in project archives. ref SDS 97 FJ5H
831517 -       ..
831518 -      [On 001121 proposed terms for using SDS to accomplish tasks under
831519 -      Doug's Guide to Running NICs. ref SDS A0 XU8I
831521 -       ..
831522 -      [On 001123 Eugene Kim submits letter from Jack Park asking for
831523 -      volunteers to summarize the project record, which seems like a
831524 -      start on the DKR. ref SDS A1 3F9O
831525 -    ..
831526 -    This aligns with need for new work role proposed to Doug on
831527 -    000301 requesting support for developing education at Stanford on a
831528 -    new discipline of "intelligence. ref SDS 36 0001  On 000317 wrote
831529 -    to Doug's SRI team on this opportunity, ref SDS 45 0005, explained
831530 -    in POIMS calling for a Communication Manager, ref OF 1 1106, which
831531 -    was submitted to Doug on 991222, ref SDS 22 6324, and further set
831532 -    out in the New World Order... ref OF 3 6369  On 000407 submitted
831533 -    recommendation, ref SDS 63 0786, that Doug use Communciation
831534 -    Metrics report citing Communiction Manager, ref DRP 2 8449, for
831535 -    developing Intelligence using SDS, to demonstrate for prospective
831536 -    sponsors, ability of Doug's DKR project to produce a new more
831537 -    useful knowledge management capability.
831538 -    ..
831539 -    Prodding contributors to resolve contradictions is part of
831540 -    feedback needed for useful "intelligence," see POIMS. ref OF 1 2200
831541 -    and ref OF 1 1106; explained more fully in NWO. ref OF 3 0936
831542 -
831543 -      Where is work product from prior DKR project meetings recorded
831544 -      beginning on 000330? ref SDS 55 7546
831545 -
831546 -      What is the plan to overcome social resistance to feedback,
831547 -      explained in the NWO...? ref OF 3 2670
831549 -       ..
831550 -      What is the plan to overcome psychological burden of looking for
831551 -      contradictions and notifying people of problems, per Pandora's
831552 -      Box issue on 000407? ref SDS 63 4757
831554 -       ..
831555 -      How much time will this assignment take per day?
831556 -      ..
831557 -      What happens when people don't respond to prodding?
831559 -       ..
831560 -      What happens when people depend on being prodded, and prodding
831561 -      gets behind, or is abandoned because accountablity is not easy
831562 -      and it is not fun?
831563 - ..
831564 - Eric commented that gathering "intelligence" is the easy part --
831565 - it is the evaluating and summarizing that is most important -- so the
831566 - intelligence community has a small army of people devoted to that
831567 - task.  This lends further weight to the concept that a SlashDot-style
831568 - system would be invaluable for DKR purposes. per Eric's 4th letter on
831569 - the meeting, ref DRP 18 0001
831571 -  ..
831572 - On 000424 Eric reported to the project team the benefits of developing
831573 - effective "intelligence" for computer programming projects like the
831574 - DKR, citing the prior Augment work. ref SDS 76 0786
831575 -
831576 -          [On 000428 received Eric's letter. ref SDS 78 1610
831577 -
831578 -          [On 000508 Eric reported that forcing himself to write up the
831579 -          record improves his understanding of what needs to be done,
831580 -          and gaps that require clarification. ref SDS 84 5938
831582 -           ..
831583 -          [On 000517 Eric Armstrong reported during at meeting Intel
831584 -          that the record he prepared on a project in Texas one year
831585 -          was helpful.  Since this was the only report of having
831586 -          prepared a record, the singularity of the effort indicates
831587 -          that it is not easy to accomplish on a regular basis.
831588 -          ref SDS 87 2064
831589 -      ..
831590 -      Need examples of "intelligence" work product and
831591 -      presentation on SlashDot and other tools that make it "easy."
831592 -
831593 -        [On 000504 Eric did not submit examples to support this
831594 -        proposition. ref SDS 82 0744
831595 -
831596 -        [On 000504 SlashDot abandoned as not supportive of project
831597 -        objectives;, ref SDS 82 5922; Zope will be tried. ref SDS 82
831598 -        5271
831600 -  ..
831601 - Eric requested more information about the "Guide to Running to a NIC".
831602 - ref DRP 18 3000
831603 -
831604 -     [On 000504 no respons has been made. ref SDS 82 3995
831605 -
831606 -
831607 -
831608 -
8317 -

SUBJECTS
WBI Transcoding Vector
WBI 3 Tier Server Architecture, 000427
Mozilla, DirectDom, JDOM Processors of XML DKR, 000427
DirectDom, JDOM Processors of XML DKR, 000427
WBI Vector Presentation, Engelbart, 000420
DirectDom Methodology Cited as Example to Guide Development of OHS/DK
Experience in SDS Develops Knowledge Representation from Meaning
XML Translate from Text, HTML, Multiple Views, 000824
Views XML Translate Email from Text, HTML, 000824

9711 -
971201 -  ..
971202 - Architecture - Three-Tier Server for WBI Implementation
971203 - Mozilla, DirectDom, JDom Support XML DKR with Processing Ops
971204 -
971205 - In the latter stages of the meeting today, Jack Park gave a report on
971206 - WBI and drew an example architecture showing how a system would use
971207 - it. (WBI would reside on a server -- either the target server or an
971208 - intermediate server -- and do the translations into "referencable
971209 - form" and manage the user's view selections.), ref DRP 17 7575
971211 -  ..
971212 - Jack suggested a possible architecture, ref DRP 17 8532, in the form
971213 - of a three-tier server:
971214 -
971215 -    •  Server -- used to run...
971216 -    •  Servlet -- runs on the server, gets HTML pages from...
971217 -    •  WBI -- converts arbitrary HTML pages or Augment pages
971218 -       into referencable/viewable form
971220 -     ..
971221 -    [On 000428 Eric submitted a letter setting out objections to
971222 -    adopting WBI for DKR support. ref SDS 78 0583
971224 -     ..
971225 -    [On 000623 Jack proposes architecure for Ontology. ref SDS 96 EK3W
971227 -     ..
971228 -    [On 001130 Jack proposes architecure to improve SDS with OHS and
971229 -    IBIS. ref SDS A2 0001
971230 - ..
971231 - In addition to WBI, Jack pointed to Mozilla, DirectDOM (nee
971232 - Weblets), and JDOM as other possible intermediary devices. Mozilla and
971233 - DirectDOM allow for browser-resident agents that manipulated the
971234 - Document Object Model (DOM) that underlies the displayed HTML. JDOM is
971235 - a mechanism put together by Jason Hunter and company that makes XML
971236 - processing transparent to a Java application and which, like the
971237 - Python EasySAX project, allows the program to manipulate a "persistent
971238 - DOM" -- a DOM resident on disk, perhaps in a database repository, so
971239 - that the entire DOM need not be resident in memory all at one time.
971241 -  ..
971242 - On 000403 Eric Armstrong wondered how Mozilla business model can be
971243 - successful. ref SDS 57 5956
971244 -
971245 -    [On 000504 Lee Iverson expanded on DOM ideas. ref SDS 82 4674
971246 -
971247 -    [On 000524 Paul Fernhout submits information on the Pointrel Data
971248 -    Repository system that is related to Python. ref SDS 89 0584
971250 -     ..
971251 -    [On 000525 Lee Iverson requests volunteers to evaluate Mozilla in
971252 -    relation to Eric Armstrong's requirements. ref SDS 90 G34I
971254 -     ..
971255 -    [On 000605 Eric plans for DDOM to incorporate changes to specs
971256 -    automatically. ref SDS 92 5084
971258 -     ..
971259 -    [On 001025 multiple views incoroporated into Doug's OHS launch
971260 -    plan. ref SDS 98 D6H8
971262 -     ..
971263 -    [On 001101 Mozilla, which is verson 5 of the Netscape browser, is
971264 -    cited, along with Linux, as example of poor productivity using open
971265 -    source methods. ref SDS 99 AS5G
971266 -
971267 -
971268 -
971269 -
9713 -

SUBJECTS
Project Planning, Objectives
Plan Needed for Guidance
Management and Governance
Agenda Issues

A206 -
A20701 -  ..
A20702 - Project "Plan" to Attract Sponsors
A20703 -
A20704 - Follow up ref SDS 71 6036, ref SDS 66 6036.
A20705 -
A20706 - There was no discussion of the project plan from work on 000324.
A20707 - ref SDS 48 9776
A20708 -
A20710 -  ..
A20711 - Meeting Agenda Planning Developed
A20712 -
A20713 - Follow up ref SDS 71 0683.
A20714 -
A20715 - No discussion of Eric's letter on 000421 citing specific issues
A20716 - discussed and agreed upon for future meetings. ref SDS 72 2442
A20718 -  ..
A20719 - No evident scheduling for...
A20720 -
A20721 -   • Werner Schaer, Software Productivity Consortium (next meeting),
A20722 -     ref DRP 12 0001
A20723 -
A20724 -   • Doug Englebart: Augment<BR> (whenever ready), ref DRP 12 8453
A20725 -
A20726 - ..
A20727 - Specific issues to discuss...
A20728 -        ..
A20729 -    1.  Use Case Scenarios
A20731 -         ..
A20732 -    2.  Evaluations of "Starter Technologies" from 00420. ref SDS 71
A20733 -        5073
A20735 -         ..
A20736 -        See discussion above on weblog tools. ref SDS 0 3944
A20738 -         ..
A20739 -    3.  Technology Roadmap
A20740 -        ..
A20741 -    4.  Transcoding Vector
A20742 -        ..
A20743 -    5.  Licensing and Business Model
A20745 -         ..
A20746 -    6.  Data Structures [I added this one.]
A20747 -
A20748 -
A20749 -
A20750 -
A20751 -
A20752 -
A208 -