CONTACTS 
0201 - Eugene Eric Kim                      650 330 1381
020101 - Mr. Eugene Eric Kim
020102 - eekim@eekim.com

SUBJECTS
Versioning Transclusion Links with Proxy Server, BrowseUp, Jack Park
SRI Linking Technology BrowseUp Demonstrated for OHS/DKR Project
BrowseUp - How it Works
BrowseUp Uses Link Server Not Proxy Server
Hyperscope Linking Presentation by Engineer from Isreal
Links Added to Web Resources Produced by Others, 010122, BrowseUp
Proxy Server Supports Third Party Links, BrowseUp, 010124, Jack Park
Linking by Point and Click ie Cut and Paste
Backlink Management
Links Without Anchors to Original Sources on Web, 010119, Doug Engelb
Collaboration Supported by BrowseUp Useful
Open Source Collaboration May be Possible with BrowseUp
BrowseUp Collaboration Open Source for Hyperscope OHS/DKR Support, Eu
BrowseUp Supports Linking Needed for Hyperscope

1816 -
1816 -    ..
1817 - Summary/Objective
1818 -
181801 - Follow up ref SDS 20 0000, ref SDS 19 0000.
181802 -
181803 - Received ref DRT 1 0001 from Eugene Kim clarifying understandings from
181804 - Jack Park's letter, ref DRP 2 0001, commenting on the meeting at SRI
181805 - where BrowseUp was demonstrated, per the letter, ref DIP 1 0001, to
181806 - the team on 000122. ref SDS 19 0001
181807 -
181808 -     [On 010127 Doug pilot testing BrowseUp. ref SDS 21 567F
181810 -      ..
181811 -     [On 010128 Alon plans beta testing BrowseUp at SRI. ref SDS 22
181812 -     0001
181814 -      ..
181815 -     [On 010131 Eugene submits requirements, uses cases and scenarios
181816 -     for OHS/DKR, and he provides tools he uses to create web pages
181817 -     with anchors and links. ref SDS 23 0001
181818 -
181819 -
181820 -
181822 -  ..
181823 - Link Server and IE Plug-in Support BrowseUp
181824 -
181825 - Follow up ref SDS 20 007P.
181826 -
181827 - Eugene cites a portion of Eric Armstrong's letter on 010123 noting
181828 - that a proxy server system, which Jack Park suggested in his letter on
181829 - 010123 is a way to imagine implementing BrosweUp, ref SDS 20 007P, was
181830 - considered by the project, and a decision was taken to use a vanilla
181831 - browser instead. ref DRT 1 0001
181832 - ..
181833 - Eugene describes BrowseUp as....
181834 -
181835 -    •  a link server, which stores these links. ref DRT 1 /A>
181836 -
181837 -       Eugene indicates that "link server" is different from a proxy
181838 -       server, ref DRT 1 VH7J, cited in Jack's letter on 010123, as a
181839 -       way to imagine how BrowseUp could be implemented. ref SDS 20
181840 -       007P  Eugene notes BrowseUp can be developed with a proxy server
181841 -       method.
181843 -          ..
181844 -         [On 010127 John Deneen encountered problems installing
181845 -         BrowseUp on Doug's computer, may try proxy server. ref SDS 21
181846 -         567F
181847 -
181848 -    •  an Internet Explorer plug-in, which downloads links from the
181849 -       link server, and overlays those links on top of the currently
181850 -       displayed web page.  The plug-in also allows you to create links
181851 -       by dragging and dropping. ref DRT 1 XK8N
181852 -  ..
181853 -    Links are....
181854 -
181855 -         granular
181856 -
181857 -         bidirectional. ref DRT 1 OK9I
181858 -
181859 -            These features align with Jack's report on 010124,
181860 -            ref SDS 20 1S8F, and on 010122. ref SDS 19 GHR2
181862 -          ..
181863 -         annotations can be assigned to links. ref DRT 1 ML9K
181864 -         ..
181865 -         quality is an attribute used for displaying available
181866 -         links, based on the frequency a link is viewed and presumably
181867 -         other information as well. ref DRT 1 0P9M
181868 -
181869 -            Frequency of being viewed aligns with the record on
181870 -            010122. ref SDS 19 RT3O
181872 -  ..
181873 - Eugene reports the BrowseUp link server is written in Java, and
181874 - apparently communicates on top of HTTP.  They were apparently designed
181875 - to be widely distributed, so that these link servers could be found
181876 - all over the Net.  BrowseUp has some solution for problems such as
181877 - link integrity and modified documents. ref DRT 1 TI4I
181879 -  ..
181880 - Eugene continues....
181881 -
181882 -    1.  Link server requirements seem to overlap with OHS/DKR project
181883 -        requirements, with some limitations and quirks.  For example,
181884 -        the thumbnails are an interesting feature, but I wonder if the
181885 -        bandwidth and storage overhead is worth it. ref DRT 1 ZF5J
181887 -         ..
181888 -        Need list and links to sources showing common requirements.
181890 -         ..
181891 -    2.  The plug-in is a win, but it's not necessarily the short-term
181892 -        direction that the core project should move in.  The link
181893 -        server would enable us to move in a number of directions, from
181894 -        browser plug-ins to proxy servers to custom clients. There's a
181895 -        lot of room for evolution here. At the meeting, Lee said that
181896 -        he would like to see a Nelson-style transclusion view of links
181897 -        and documents (where documents are displayed side by side, with
181898 -        lines showing the interconnected links).  I see no reason why
181899 -        such a view is not possible using BrowseUp's underlying system;
181900 -        they just haven't built it yet. ref DRT 1 HH5O
181901 -
181902 -           Seems to align with Jack Park's correlation on 010124
181903 -           between BrowseUp and tranclusions. ref SDS 20 007P
181905 -            ..
181906 -           On 010122 Lee Iverson recommended BrowseUp add value to
181907 -           handling daily working information. ref SDS 19 NN5G
181909 -            ..
181910 -           [On010127 report that Doug concurs with Eugene's analysis.
181911 -           ref SDS 21 ZS5K
181912 -        ..
181913 -    3.  Collaboration is highly desirable, and a reasonable
181914 -        possibility.  Alon seemed genuinely interested in seeing link
181915 -        databases pop up all over the world, and seemed open to the
181916 -        possibility of open sourcing parts or all of their system in
181917 -        order to enable this (and collaborate with us). ref DRT 1 7M6O
181918 -
181919 -           Eugene's planning aligns with goals for Hyperscope set out
181920 -           by Doug in the OHS Launch Plan on 001025. ref SDS 13 ADK1
181922 -            ..
181923 -           Aligns with the record on 010122. ref SDS 19 QS4L
181925 -            ..
181926 -           [On 010127 report that Doug supports Eugene's analysis.
181927 -           ref SDS 21 4EWC
181929 -            ..
181930 -           [On 010128 Alon plans beta testing BrowseUp at SRI.
181931 -           ref SDS 22 0001
181932 -
181933 -
181934 -
1820 -

SUBJECTS
Links Added to Other People's Internet Property Illegal, BrowsUp
BrowseUp Adds Links from One Person's Internet Property to Someone's
Proxy Server Links Web Pages, EBay, Illegal, Risky, Jack Park
BrowseUp Bidirectional Linking Presents Important Social Consequences
Back Link Management

3107 -
310801 -  ..
310802 - Pandora's Box of Risk from Adding Links to Original Work
310803 -
310804 - Follow up ref SDS 20 00FO, ref SDS 19 GHR2
310805 -
310806 - Eugene notes, without specific reference, discussion about social
310807 - consequences of unrestricted linking that was interesting and
310808 - important. ref DRT 1 GJ4O
310809 -
310810 -    On 010122 back-link issues were cited. ref SDS 19 HS9J
310812 -     ..
310813 -    On 010124 Jack Park submitted analysis indicated a "pandora's box"
310814 -    of property right issues are presented. ref SDS 20 00FO
310815 -
310816 -      [On 010131 Eugene Kim submitted references that describe the main
310817 -      problem to solve for developing OHS is lack of simple, standard,
310818 -      machine-readable ways for associating related information.
310819 -      ref SDS 23 SW4O
310820 -
310821 -
310822 -
310823 -
310824 -
3109 -

SUBJECTS
Open Source Collaboration May be Possible with BrowseUp
BrowseUp Collaboration Open Source for Hyperscope OHS/DKR Support, Eu
BrowseUp Open Source Collaboration, Doug Engelbart Pursuing, Eugene K
BrowseUp Used by OHS/DKR Team to Learn about Linking that Helps Devel
Usability Study to Promote OHS/DKR with Example BrowseUp Improves Pro
Co-evolution Education KM, 000301
BrowseUp Pilot Test Lean Linking Requirements, Eugene Kim, 010125

3909 -
391001 -  ..
391002 - Planning Follow Up Action with BrowseUp
391003 -
391004 - Eugene reports that Doug is pursuing collaboration with BrowseUp.
391005 - ref DRT 1 8W3K
391006 -
391007 -     [On 010127 report of consideration for collaboration with
391008 -     BrowseUp. ref SDS 21 4EWC
391010 -  ..
391011 - Eugene recommends team try BrowseUp to learn about linking features, ,
391012 - ref DRT 1 GM4F, which which could lead to....
391013 -
391014 -    4. a refinement of requirements for the OHS
391015 -
391016 -    5. formal usability studies, which could also help refine
391017 -       requirements (part of the coevolution strategy) as well as serve
391018 -       as a marketing vehicle for some of the OHS's features. (i.e.
391019 -       "Studies showed that link typing improved productivity by
391020 -       512%.")
391022 -  ..
391023 - The recommendation to try BrowseUp aligns with the record on 010122,
391024 - ref SDS 19 A84M, and earlier ideas on 001126 to gain experience using
391025 - IT tools for learning about KM. ref SDS 15 QW8I
391026 -
391027 -     [On 010127 report that Doug is setting up BrowseUp for test
391028 -     application. ref SDS 21 567F
391030 -      ..
391031 -     [On 010128 Alon plans beta testing BrowseUp at SRI. ref SDS 22
391032 -     0001
391034 -      ..
391035 -     [On 010131 Eugene submits requirements, uses cases and scenarios
391036 -     for OHS/DKR, and he provides tools he uses to create web pages
391037 -     with anchors and links. ref SDS 23 0001
391038 -
391039 -
391040 -
391041 -
391042 -
391043 -
391044 -
391045 -
391046 -
391047 -
391048 -
391049 -
391050 -