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 20 0000, ref SDS 12 0000.
040502 -
040503 - Did not attend the meeting.  Received account from people who did
040504 - attend, including Eric's letter today, ref DRT 1 0001
040505 -
040506 -
040507 -
040508 -
040509 -
040510 -
040511 -
0406 -

SUBJECTS
SRI Organizational Platform, Project Management
Project Manager
Management and Governance
SRI Organizational Platform, Doug, 000419
SRI Project Management, Doug, 000419
DKR Project Management
SRI Organizational Platform, Project Management, 000419
Plan Needed for Guidance
Project Management
Iverson, Lee Assigned Full Time by SRI
Iverson, Lee Assigned Full Time to DKR Project
Assigned Full Time to DKR Project

1714 -
1715 - Discussion
171601 -  ..
171602 - Introductions - Diverse Skills Focused on DKR Project
171603 - Lee Iverson Assigned Full Time by SIR on DKR Project
171604 -
171605 - Follow up ref SDS 20 2079, ref SDS 12 2079.
171606 -
171607 - New attendee from Lochkeed Martin.
171608 - ..
171609 - Lee Iverson
171610 -
171611 -     ...has been given the go-ahead to work on this project, so he has
171612 -     been able to devote some quality time to it. ref DRT 1 6882
171613 -
171614 -     This aligns with Doug Engelbart's report on 000419 that SRI will
171615 -     take the lead in managing the project. ref SDS 10 1540
171616 -
171617 -        What is Lee's assignment?  To follow Doug's instruction; to
171618 -        build a DKR; to investigate DKR designs and report on viability
171619 -        of a project to build a DKR?
171621 -         ..
171622 -        How does Lee's assignment impact project management, decisions
171623 -        on objectives, architecture, assignments, resources to manage
171624 -        and carry on the work?
171625 -        ..
171626 -        Does this mean the project now has some resources?
171627 -
171628 -           [On 000505 spec review suggests need for "listening"
171629 -           capability, which may get attention from elevated support by
171630 -           SRI expertise in project management, presaged by Lee's new
171631 -           assignment today. ref SDS 26 1770
171632 -
171633 -
171634 -
171635 -
171636 -
171637 -
1717 -

SUBJECTS
Project Planning, Objectives
Plan Needed for Guidance
Management and Governance
Agenda Issues
Sponsor/Stakeholder Planning
Killer Application

2508 -
250901 -  ..
250902 - Search for "Killer App" Focuses on Knowledge/Enterprise Management
250903 - Sponsors Looking for Projects in Knowledge Management Arena
250904 -
250905 - Follow up ref SDS 20 4877, ref SDS 12 4877.
250906 -
250907 -    At the end of the meeting on 000413 Eric seemed to indicate plans
250908 -    to consider sponsor outreach to develop funding, at the meeting
250909 -    today, perhaps including results of Doug's meeting with SRI and a
250910 -    major potential sponsor on Monday, 000410, ref SDS 9 4877, which
250911 -    was reported on 000419 to be moved to 000425.
250913 -     ..
250914 -    This task was evidently not done today.
250915 -
250916 -
250918 -  ..
250919 - Project "Plan" to Attract Sponsors
250920 -
250921 - Follow up ref SDS 20 6036, ref SDS 12 6036.
250922 -
250923 - There was no discussion of the project plan from work on 000324.
250924 - ref SDS 5 9776
250926 -  ..
250927 - On 000419 Doug announced plans for a trip to Washington for sponsor
250928 - support.  At the meeting on 000420 Eric set objective to provide
250929 - proposal ideas to support Doug's trip, that shows a project
250930 - development plan. ref SDS 12 8667
250932 -  ..
250933 - Proposal ideas for Doug's trip were evidently not discussed today.
250934 -
250935 -     [On 000601 Doug Engelbart and Pat Lincoln reported progress in
250936 -     fund raising that shows need for stronger effort. ref SDS 33 4877
250937 -
250938 -     [On 000601 Doug and Pat requested ideas from team to prepare a
250939 -     summary of project objectives and initial deliverables, for
250940 -     presenting to propspective sponsors who can provide development
250941 -     funds. ref SDS 33 0852
250942 -
250943 -
250944 -
250945 -
250946 -
250947 -
2510 -

SUBJECTS
DKR Starter Technologies, 000504
ZWiki-style Collaborative Document System, 000427
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
DKR Starter Technologies, Email, Begin Using a System, 000504
Wiki Starter Technologies for OHS/DKR, 000504
Wiki Proposed for KM, Lee Iverson
ZWiki Zope Applies Wiki Technology

4916 -
491701 -     ..
491702 -    SlashDot, Arsdigita Ruled Out for Project Email Support
491703 -
491704 -    Follow up ref SDS 20 5985.
491705 -
491706 -    On 991222 review of Doug Engelbart's work, at Doug's request,
491707 -    showed that pilot testing is required to evaluate new capabilities
491708 -    for enabling the OHS/DKR vision.  The record today reviews results
491709 -    from pilot testing various methods.
491711 -     ..
491712 -    Eric drew from the meeting today that it seems reasonable to rule
491713 -    out Slashdot, PHP/Slashdot, and Arsdigita based on language and
491714 -    installation issues. ref DRT 1 2419
491716 -     ..
491717 -    On 000427 SlashDot was planned for making it easy to gather useful
491718 -    "intelligence." ref SDS 20 3685
491719 -
491721 -     ..
491722 -    Zope Easy to Install, Strong Email for DKR Project, Uses Python
491723 -    Starter Tools for DKR Email, Project Team to Pilot Test
491724 -    Pilot Test Email Programs to Evaluate DKR Starter Technologies
491725 -
491726 -    Follow up ref SDS 20 3944, ref SDS 11 4877.
491727 -
491728 -    Lee has installed Zope, ref DRT 1 3312, in addition to SlashDot
491729 -    reported in the meeting on 000427. ref SDS 20 5985  Zope was easy
491730 -    to install and seems highly usable, providing a strong candidate
491731 -    for a starter technology to support project email. ref DRT 1 3312
491733 -     ..
491734 -    Zope uses Python and acts as its own server. ref DRT 1 1792
491735 -
491736 -        [On 000516 Lee Iverson setting Zope/Wiki server for the
491737 -        project. ref SDS 29 4971
491738 -
491739 -        [On 000524 Paul Fernhout submits information on Pointrel Data
491740 -        Repository system that is implemented in Python; may provide
491741 -        development path with Zope. ref SDS 31 0584
491742 -
491744 -     ..
491745 -    Wiki-Style Collaborative Doc Management Supported by Zope
491746 -
491747 -    Follow up ref SDS 20 9000.
491748 -
491749 -    Zope is developing a "Portal Tool Kit" including newsgroups, mail
491750 -    lists, and the Wiki (anyone can edit your web page) collaborative
491751 -    editing system.  All of which makes it an interesting vehicle for
491752 -    use and/or hacking. ref DRT 1 0924
491753 -
491754 -           [On 000505 project requirements for OHS, which Eric is
491755 -           calling a CDS, needs to incorporate planning to begin by
491756 -           pilot testing starter technologies. ref SDS 26 2852
491758 -            ..
491759 -           [On 000516 Lee Iverson setting up Zope/Wiki server for the
491760 -           project. ref SDS 29 6935
491762 -            ..
491763 -           [On 000518 Lee reports Zope up and running. ref SDS 30 3944
491764 -
491766 -         ..
491767 -        Intelligence Gathering Procedure using Zope?
491768 -
491769 -        Will Zope be as effective as SlashDot for making it easy to
491770 -        gather "intelligence," as reported on 000427? ref SDS 20 3685
491771 -
491772 -        How will Zope be used to gather "intelligence."
491773 -
491774 -           [On 000525 Lee reports Zope difficult to use. ref SDS 32
491775 -           3944
491777 -            ..
491778 -           [On 000609 Lee has Wiki up and running for use by project
491779 -           team. ref SDS 35 0001
491781 -            ..
491782 -           [On 000618 Lee explains social contract procedures for using
491783 -           Wiki to manage the project. ref SDS 36 9000
491784 -
491785 -
491787 -     ..
491788 -    JavaCorporate Suite Option for Improving Email
491789 -
491790 -    JavaCorporate suite of collaboration tools is the only other
491791 -    viable candidate for improving the project's email sytem.
491792 -    ref DRT 1 8686
491793 -
491794 -    JavaCorporate uses Java and uses the Apache server.
491796 -     ..
491797 -    Zope, JavaCorprate Good Options for Processing XML Structures
491798 -
491799 -    Which design, Zope or JavaCorporate, is more modular and hackable
491800 -    remains to be seen. ref DRT 1 1860
491801 -
491802 -    Eric concludes from the meeting today that the project has good
491803 -    options for processing XML structures.
491804 -
491805 -
491806 -
491807 -
491808 -
491809 -
4919 -

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

5706 -
570701 -  ..
570702 - Server Space for DKR Donated by Sun Microsystems
570703 -
570704 - Follow up ref SDS 20 5962, ref SDS 12 5962.
570705 -
570706 - No report of progress using server donated by Sun, per Eric's letter
570707 - on 00042, ref SDS 13 0001
570708 -
570709 -
570710 -
570711 -
570712 -
5708 -

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

6206 -
620701 -  ..
620702 - Legal Issues Arising from Open Source and Sponsor Support
620703 -
620704 - Follow up ref SDS 20 3055, ref SDS 12 3055.
620705 -
620706 - There was no discussion on getting a license or other standing
620707 - required to operate, noted at the meeting on 000330, ref SDS 7 3995,
620708 - possibly because decision has been taken for SRI to provide an
620709 - organizational platform from meeting on 000420, ref SDS 12 6630, and
620710 - assignment of Lee Iverson with SRI to support the DKR effort full
620711 - time, per above. ref SDS 0 7743
620713 -  ..
620714 - There was no discussion for licensing options discussed on 000324, and
620715 - submission by Eric Armstrong of license ideas on 000421 ref SDS 13
620716 - 3055
620717 -
620718 -
620719 -
620720 -
620721 -
6208 -

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
NSF Denied Support, Wanted Definition of Knowledge
Knowledge Workup Like Bellinger, Doug Engelbart

7815 -
781601 -  ..
781602 - Project Objective to Produce DKR Capability
781603 -
781604 - Follow up ref SDS 20 2808, ref SDS 12 2808.
781605 -
781607 -     ..
781608 -    Knowledge Management Definition
781609 -
781610 -    Follow up ref SDS 20 5555, ref SDS 12 5555.
781611 -
781612 -    Prior to the meeting, Eugene Kim submitted explanation for
781613 -    "information" and "knowledge" based on experience doing research
781614 -    and developing a DKR. ref SDS 25 5003  This work was evidently not
781615 -    discussed during the meeting today.
781616 -
781617 -        [On 000615 OHS/DKR team discouraged nobody knows what we are
781618 -        trying to accomplish, lack of progress causes engineers to
781619 -        give up on Knowledge Management; decide to improve email and
781620 -        call it OHS/DKR. ref SDS 36 6271
781622 -         ..
781623 -        [On 001126 Eugene proposed learning about KM by using greater
781624 -        diligence applying IT rather than use SDS. ref SDS 38 QW8I
781626 -     ..
781627 -    Doug Engelbart reported that NSF did not support his research
781628 -    because SRI's proposal did not define knowledge, which reflects
781629 -    fear expressed by Eric Armstrong yesterday on 000503 that
781630 -    "knowledge" is a marketing effort rather than a concept for
781631 -    improving information technology. ref SDS 24 5033
781632 -
781633 -        [On 000510 letter from Joe Williams reports Doug's comments on
781634 -        needing definition of knowledge for NSF proposal; Joe also
781635 -        submits an explanation of knowledge. ref SDS 28 0004
781637 -     ..
781638 -    NSF's requirement for definition of "knowledge" to support award of
781639 -    research funding, aligns with Doug's request on 000307 for a work
781640 -    up on knowledge and KM similar to Bellinger, ref SDS 4 4820, and
781641 -    again on 000419. ref SDS 10 4964
781642 -
781643 -        [On 000518 Professor Mary Keeler presented explanation of
781644 -        "knowledge" from the philosophy of Charles Peirce's work that
781645 -        relies on experience, similar to cognitive science. ref SDS 30
781646 -        8439
781648 -         ..
781649 -        [On 000615 project team defers DKR because not enough known
781650 -        about "knowledge" and KM. ref SDS 36 6271
781652 -         ..
781653 -        [On 001025 OHS Launch Plan omits this definition. ref SDS 37
781654 -        A4U2
781656 -         ..
781657 -        [On 011102 article history Knowledge Management by Larry
781658 -        Prusak, Directory of Knowledge Management at IBM cites defining
781659 -        Knowledge Management has proven defficult to accomplish; there
781660 -        can be no tools, theories, methods, and practices without a
781661 -        definition. ref SDS 39 L73H
781663 -         ..
781664 -        [On 011102 Prusak article 11 Deadly Sins Knowledge Management
781665 -        lists failure to define knowledge. ref SDS 39 CQ5M
781667 -     ..
781668 -    No report on Debra England's suggestion on 000420 for team members
781669 -    to write up the purpose of the project, ref SDS 12 5555, to
781670 -    identify core function of DKR, called out by Eric on 000208.
781671 -    ref SDS 3 8960
781673 -     ..
781674 -    No evident discussion of Eric's submission on 000421, ref SDS 13
781675 -    5933, supplemented on 000423 proposing that the DKR augment human
781676 -    intellignece, ref SDS 16 5933; nor of Adam Cheyer's submission on
781677 -    000424, proposing that Doug's name be incorporated into the project
781678 -    mission statement. ref SDS 17 0002
781680 -     ..
781681 -    Discussion above on using Zope to strengthen project email in place
781682 -    of SlashDot for gathering intelligence, reflects Eric's idea on
781683 -    000423, ref SDS 16 5943, to improve email as a first step to
781684 -    accomplish the purpose of the project to augment intelligence.
781685 -    ref SDS 0 9000
781686 -
781688 -     ..
781689 -    Editor Based on XML Initial Project Deliverable Enhance Email
781690 -    Collaborative Document System and OHS Supported by Editor
781691 -
781692 -    Follow up ref SDS 20 5880, ref SDS 12 5880.
781693 -
781694 -    No record of discussion, but on 000423 Eric proposes in a letter to
781695 -    the team that the purpose of the DKR project, which he says is to
781696 -    enhance human intelligence, ref SDS 16 5096, can be accomplished by
781697 -    an enhanced email program. ref SDS 16 5943  Enhancing email as
781698 -    initial objective was set by Doug on 000326, ref SDS 6 5972, and
781699 -    confirmed on 000405. ref SDS 8 2484
781701 -     ..
781702 -    On 000503 significant discussion between Jack and Eric on project
781703 -    scope with respect to DKR and email. ref SDS 24 0001
781704 -
781706 -     ..
781707 -    Atomic Data Structures Derive from Fundamental Information Unit
781708 -    Fundamental Information Unit Focuses DKR Design Effort
781709 -
781710 -    Follow up ref SDS 20 4004, ref SDS 12 4004.
781711 -
781712 -    No evident discussion today of Joe Williams comprehensive
781713 -    presentation on 000420 of DKR and OHS framework. ref SDS 12 4004
781715 -     ..
781716 -    No discussion of atomic data structures submitted by Eric on
781717 -    000423. ref SDS 16 4977
781718 -
781719 -
781720 -
7818 -

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

8305 -
830601 -  ..
830602 - Use Case Methods for Software Design
830603 -
830604 - Follow up ref SDS 20 4933, ref SDS 12 4933.
830605 -
830606 - No record of discusion on Eugene Kim's comprehensive submission today
830607 - on the scope of OHS, and detailing specific use cases that improve
830608 - literacy, supported by Jack Park. ref SDS 25 0784
830610 -  ..
830611 - The advantage of literacy using alphabet technology for augmenting
830612 - human intelligence was reviewed on 000120, ref SDS 2 5976, citing
830613 - work on 991108 showing this method has been the core capability of
830614 - knowledge management that has lifted civilization for the past 2,000
830615 - years. ref SDS 1 0300
830616 -
830617 -
830618 -
830619 -
8307 -

SUBJECTS
WBI Transcoding Vector
Engelbart, Doug
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
WBI 3 Tier Server Architecture, 000427
Mozilla, DirectDom, JDOM Processors of XML DKR, 000427
DirectDom, JDOM Processors of XML DKR, 000427
Park, Jack
WBI Vector Presentation, Engelbart, 000420
W3C DOM Ineffective for Data Base
W3C Ineffective DOM Support, 000504
Python DOM Support, 000504
Java DOM Support, 000504

AA17 -
AA1801 -  ..
AA1802 - Guide to Running NICs Gathers Intelligence, Provides Feedback
AA1803 - WBI Transcoding Vector Records Information, Gathers Intelligence
AA1804 - Communication Manager Proposed to Compliment Tools for DKR
AA1805 -
AA1806 - Follow up ref SDS 20 3995, ref SDS 12 3995.
AA1807 -
AA1808 - Nothing has been submitted on Eric's request in his letter on 000428
AA1809 - for more information on a Guide to Running a NIC, ref DRP 3 3000,
AA1810 - proposed at the meeting on 000427. ref SDS 20 2867
AA1811 - ..
AA1812 - No record of work product showing contradictions and prodding of
AA1813 - contributors to grow knowledge repository's capabilities as we use it,
AA1814 - also proposed on 000427. ref SDS 20 2867
AA1815 - ..
AA1816 - No evident submission of examples showing "intelligence" is easy
AA1817 - to gather, and that a SlashDot-style system would be invaluable for
AA1818 - DKR purposes proposed on 000427. ref SDS 20 3685
AA1820 -  ..
AA1821 - No evident follow up on Doug's presentation for WBI Transcoding plan,
AA1822 - proposing a new initiative for a Guide to Running NICs, reported at
AA1823 - the meeting on 000427. ref SDS 20 3995
AA1824 -
AA1825 -
AA1827 -  ..
AA1828 - Architecture - Three-Tier Server for WBI Implementation
AA1829 - DirectDom, JDom Support XML DKR with Processing Ops
AA1830 -
AA1831 - Follow up ref SDS 20 4674.
AA1832 -
AA1833 - There is nothing in the record for a plan, schedule and assignments to
AA1834 - accomplish the three primary tasks for developing an architecture for
AA1835 - the OHS and/or DKR, reported on 000426. ref SDS 18 0304
AA1836 -
AA1838 -     ..
AA1839 -    Fundamental Issues of DKR Project Focused by DOM
AA1840 -    DOM (Document Object Model) Uses XML for Doc Management
AA1841 -
AA1842 -    Eric's letter received following the meeting today, reports that...
AA1843 -
AA1844 -    Lee Iverson explained XML tools can use a lot of mechanisms for
AA1845 -    manipulating Document Object Model (DOM) trees (basically, the
AA1846 -    tree-structured form of a document), to support a...
AA1847 -
AA1849 -                      ..
AA1850 -                     Distributed* DOM or DDOM
AA1851 -
AA1853 -     ..
AA1854 -    This seems to build on Jack Park's presentation at the meeting on
AA1855 -    000427. ref SDS 20 1092
AA1856 -
AA1857 -        [On 000605 Eric submitted changes to create v0.8 of project
AA1858 -        specs; advises that DDOM will automatically incorporate
AA1859 -        changes into specs. ref SDS 34 5084
AA1861 -     ..
AA1862 -    Casting the problem in those terms immediately implies the need for
AA1863 -    node versioning, attribution tracking, and most of the other
AA1864 -    requirements previously identified for the system (while at the
AA1865 -    same time providing the mechanisms that can be used to fulfill
AA1866 -    those requirements). ref DRT 1 0001
AA1868 -     ..
AA1869 -    Attendees feel DDOM provides a brilliant focus to fundamental
AA1870 -    issues. ref DRT 1 4941
AA1871 -
AA1872 -        How does DOM relate to the meaning of "knowledge."
AA1873 -
AA1874 -        In a letter on April 26, 2000 Jack Park noted the purpose of
AA1875 -        the project is to develop a dynamic knowledge repository,
AA1876 -        ref SDS 18 4940, and asked rhetorically...
AA1877 -
AA1879 -                            ..
AA1880 -                           What the hell is that?
AA1881 -
AA1883 -         ..
AA1884 -        On 000307 Doug Engelbart asked the project team to prepare a
AA1885 -        work up on the meaning of "knowledge," "information,"
AA1886 -        "learning," leading to foundational understanding of "knowledge
AA1887 -        management". ref SDS 4 4820  Earlier on 000120 this task was
AA1888 -        posed to the project. ref SDS 2 5063  On 000419 Doug requested
AA1889 -        again that the team define "knowledge." ref SDS 10 4964
AA1891 -         ..
AA1892 -        On 000503 Eric Armstrong proposed setting aside these questions
AA1893 -        about "knowledge." ref SDS 24 5033
AA1895 -         ..
AA1896 -        Since the assignment of the project is to create a knowledge
AA1897 -        management support, developing a working definition of
AA1898 -        knowledge is a fundamental predicate to evaluating how DOM or
AA1899 -        other technologies might support the project.
AA1900 -
AA1902 -     ..
AA1903 -    W3C DOM Ineffective for Data Base; Python, Java Support Database
AA1904 -
AA1905 -    Follow up ref SDS 22 1066.
AA1906 -
AA1907 -    The w3c DOM standard puts the whole DOM into memory at once -- fine
AA1908 -    for documents, but pretty horrible when your "DOM" is in fact a
AA1909 -    disk-resident database. Python has a (badly named) EasySAX model
AA1910 -    that lets you instantiate only the subtree you need in memory. (SAX
AA1911 -    is the Simple API for XML. It's another way of processing XML. But
AA1912 -    "SmallDOM' would have been a better name.) Meanwhile, Java has a
AA1913 -    JDOM model that lets you do the same thing. ref DRT 1 1012
AA1914 -
AA1916 -     ..
AA1917 -    Transcoding Supported by DOM
AA1918 -
AA1919 -    During the discussion of the DDOM concept, Eugene pointed out that
AA1920 -    identifying the fundamental XML structure was the core issue. Given
AA1921 -    that, we can translate or transcode other data formats to it. The
AA1922 -    difference is one of persistence. If data starts out in form X, and
AA1923 -    I translate it to form Y, then forever after it is in form Y. But
AA1924 -    if I transcode it to form Y, then it stays in form X and is
AA1925 -    transcoded to form Y whenever I need it. ref DRT 1 1200
AA1926 -
AA1928 -     ..
AA1929 -    Augment Data can be Transcoded
AA1930 -
AA1931 -    Eric observed that Augment data could be transcoded into "normal
AA1932 -    form" used in the repository.  That would work because, unlike HTML
AA1933 -    pages, information segments in the Augment database have fixed IDs
AA1934 -    -- so adding or modifying data in the repository would not shuffle
AA1935 -    IDs around. (An innocuous edit to an HTML page, on the other hand,
AA1936 -    could turn previously created links into gibberish. The links would
AA1937 -    "succeed", but be be pointing to the wrong paragraphs.),
AA1938 -    ref DRT 1 6278
AA1939 -
AA1940 -
AA1942 -     ..
AA1943 -    Gnutella Eliminates Browser/Server Distinction
AA1944 -
AA1945 -    On the way out the door, Lee observed that the whole DDOM could
AA1946 -    well be built on a Gnutella foundation in order to eliminate the
AA1947 -    browser/server distinction. A person's repository would then act as
AA1948 -    server as well as a client application. That is exactly how the
AA1949 -    ideal system must operate, so that prospect was rather exciting, as
AA1950 -    well. ref DRT 1 1188
AA1952 -     ..
AA1953 -    Lee suggested "wrapping" the Gnutella interface in a layer of
AA1954 -    function calls, so that we could replace Gnutella with a different
AA1955 -    system merely by rewriting the function library (rather than
AA1956 -    modifying the system). But that is straight forward system-design
AA1957 -    stuff. ref DRT 1 1650
AA1958 -
AA1959 -
AA1960 -
AA1961 -
AA1962 -
AA20 -