CONTACTS 

SUBJECTS
Links Added to Other People's Internet Property Illegal, BrowsUp, 010
Objections Transcoding, IBM's WBI, 000428
Links Illegal Added to Someone's Property on Internet, BrowseUp, 0101
Links Added to Other People's Work Product on Internet, BrowseUp, 010
Proxy Server for Linking Discussed by OHS Team Previously
Vanilla Browser Discussed by OHS Team Previously
BrowseUp Supports Linking Needed for Hyperscope

1609 -
1609 -    ..
1610 - Summary/Objective
1611 -
161101 - Follow up ref SDS 19 0000.
161102 -
161103 - Received ref DRT 1 0001 from Jack Park commenting on the meeting at
161104 - SRI where BrowseUp was demonstrated, per the letter, ref DIP 1 0001,
161105 - to the team on 000122. ref SDS 19 0001
161107 -  ..
161108 - Jack says BrowseUp is very innovative and well done. Much of what
161109 - BrowseUp does has been anticipated in papers by Douglas Engelbart, Ted
161110 - Nelson, and Francis Heylighen, among others.  Nevertheless, as an
161111 - execution of the many ideas, BrowseUp is really slick. ref DRT 1 I16H
161112 -
161113 -    Jack does not provide an explanation nor sources showing prior work
161114 -    on BrowseUp "innovations."
161115 -
161116 -
161118 -  ..
161119 - Proxy Links Considered Previously by DKR Team
161120 - BrowseUp Linking Similar to Transclusion Proposed by Ted Nelson
161121 -
161122 - Jack explains BrowseUp is close to Transclusion technology described
161123 - by Ted Nelson. ref DRT 1 006M   "Transclusion" was reviewed on 000305
161124 - along with Xanadu. ref SDS 4 4725
161125 -
161126 -        [On 010125 Eugene Kim recalled that Lee Iverson proposed a
161127 -        Nelson-style transclusion view of links and documents (where
161128 -        documents are displayed side by side, with lines showing the
161129 -        interconnected links), would be useful. ref SDS 20 KC8H
161131 -         ..
161132 -        [On 020920 Jack associates transclusion with cut and paste.
161133 -        ref SDS 23 0E62
161135 -      ..
161136 -     Jack says BrowseUp does not actually insert the referenced
161137 -     material into the page being displayed.  Rather, it gives you the
161138 -     equivalent of a menu to select those links you might want to
161139 -     browse. ref DRT 1 006M
161141 -  ..
161142 - Jack imagines a browser set to work through a proxy server, a tiny
161143 - local server that, itself, does the web connection for the browser.
161144 -
161145 -     [On 010125 Eugene says BrowseUp uses a link server, rather than a
161146 -     proxy server. ref SDS 20 ZW3N
161147 -
161148 -     [On 010127 John Deneen encountered difficulty setting up BrowseUp
161149 -     on Doug's computer, may try a proxy server. ref SDS 21 567F
161151 -  ..
161152 - WBI, IBM's transcoding engine, is one such server. ref DRT 1 007P
161153 -
161154 -     WBI was presented to OHS/DKR team at SRI on 000413. ref SDS 6
161155 -     5148
161157 -  ..
161158 - Eric Armstrong reports in a separate letter that the OHS/DKR team
161159 - discussed a design similar to the proxy server scheme Jack attrubutes
161160 - to BrowseUp.  Eric says having an intelligent proxy on the client
161161 - opens a lot of doors, and BrowseUp appears to have to taken that
161162 - avenue to the best possible conclusion. ref DRT 2 N25M
161163 -
161164 -      Eric recalls, the group disliked that notion, because we wanted
161165 -      people to use a "vanilla browser", without having to do anything
161166 -      special to the client. ref DRT 2 RV6J
161167 -
161168 -         No links to original sources are provided to clarify proxy
161169 -         server and vanilla browser.  On 000824 Eric is not a fan of
161170 -         links to the archives. ref SDS 10 7O9I
161172 -          ..
161173 -         Eric's letter on 000824 discussed a "vanilla" client."
161174 -         ref SDS 10 FJ8H
161176 -       ..
161177 -      Eric asks how much effort is it to install that proxy?
161178 -
161179 -         Is it transparent?
161180 -
161181 -         Does a remote server provide the "proxy", so that you have to
161182 -         visit that server and, from there, go to other points on the
161183 -         Web? ref DRT 2 JX7H
161185 -  ..
161186 - Jack continues -- the browser does not directly interact with the web;
161187 - therefore, the proxy server has the opportunity to look at the URL
161188 - requested, and feed that URL to another web connection, which happens
161189 - to be BrowseUp's link server.  The link server can download what it
161190 - knows about the selected URL while the selected URL, itself, is coming
161191 - in on another http connection.  Now, two bodies of html information
161192 - are available in the proxy server.  Before the server sends that to
161193 - the requesting browser, it can perform whatever computation it likes.
161194 - ref DRT 1 U67I
161196 -  ..
161197 - Jack says that BrowseUp [transclusion] appears to add a tiny bit of
161198 - html to the page before being displayed.  That added html forms an h
161199 - ref link such that, should you click on it, you now go directly
161200 - (through the proxy server, of course) to some URL inside the link
161201 - server, where another window opens complete with all links others have
161202 - established with the link you just clicked on. ref DRT 1 4P8H
161203 -
161204 -     This sounds like it requires everyone to use a BrowseUp program
161205 -     and the same server to create and access links.
161207 -      ..
161208 -     Is the HTML added to the original file?
161209 -
161210 -         If so, this seems to conflict with Jack's planning on 000623
161211 -         to not disturb original work. ref SDS 9 5475
161213 -      ..
161214 -     If people use different servers, they will not see the same
161215 -     links???
161217 -      ..
161218 -     What controls selection of the server where this stuff is stored,
161219 -     and how is that server managed by the user and the BrowseUp
161220 -     program?
161222 -      ..
161223 -     Can it be done locally, so each person creates and maintains their
161224 -     own links to other desired locations, but that does not impact
161225 -     what other people see?
161227 -  ..
161228 - Jack suggests a proxy server could open a tiny dialog window of its
161229 - own for reaching into a browser image and dragging something into the
161230 - new dialog box. ref DRT 1 004M
161231 -
161232 -     That establishes a target.
161233 -
161234 -     Go to another web page and click on something.
161236 -      ..
161237 -     The proxy server opens a display of linkages you are about to
161238 -     make.
161240 -      ..
161241 -     Both directions are linked, but you can 'uncheck' a box at either
161242 -     to break a link.
161244 -      ..
161245 -     You can annotate the link(s), complete with search words and so
161246 -     forth.
161247 -
161248 -
161249 -
1613 -

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
Original Source Change Without Permision Illegal Links Proxy Server,
Original Source Changes Improper Counterproductive Shows Bad Faith
Original Sources Can Only Be Changed by Authors
Original Sources Changed Only by Author

3209 -
321001 -  ..
321002 - Pandora's Box of Risk from Adding Links to Original Work
321003 -
321004 - Follow up ref SDS 19 GHR2
321005 -
321006 - Jack cites a 'web of trust' concept advanced by Tim Berners-Lee in his
321007 - Semantic Web initiative.
321008 -
321009 -     There is no link to clarify this association in Jack's letter.
321011 -  ..
321012 - Jack says BrowseUp opens pandora's box to harmful things one could do
321013 - to someone else's work product on the Internet; for instance, someone
321014 - linking your home page heading to, say, a really grotesque gif or jpg.
321015 - ref DRT 1 00FO
321016 -
321017 -     On 000221 Jack explained that ontology is a pandora's box of
321018 -     complexity. ref SDS 3 3248
321020 -      ..
321021 -     [On 010125 Eugene Kim reports understandings that BrowswUp
321022 -     supports bidirectional linking. ref SDS 20 HV5H
321024 -      ..
321025 -     [On 010125 Eugene notes social consequences. ref SDS 20 A0FO
321027 -      ..
321028 -     [On 010620 Lee Iversion proposes requirements for NODAL and CDR
321029 -     that include granular addressability, which may relate to concerns
321030 -     Jack raises today about BrowseUp. ref SDS 22 FW6L
321031 -
321033 -  ..
321034 - Jack suggests considering rules that links ought to be a priviliged
321035 - operation that requires express authorization. ref DRT 1 JH5L
321036 -
321037 -     Need clarification, that somone can create links to and from
321038 -     anything, so long as it is maintained locally, and is not imposed
321039 -     on another person's work product.
321041 -      ..
321042 -     SDS uses this method.  It has lots of links and makes lots of
321043 -     associations with attribution and context.  It does not change
321044 -     anyone's original work.
321045 -
321046 -         The issue seems to be where someone adds links that add to an
321047 -         orginal work something that directs attention of others
321048 -         differently from the intent of the author, discussed on
321049 -         010122. ref SDS 19 GHR2
321050 -
321052 -      ..
321053 -     Intranets Provide Control for Third Party Links
321054 -     Third Party Links Traceable through Logs
321055 -
321056 -     Jack says corporate intranets operate under a web of trust.  On
321057 -     networked improvement communities (NICs), the opportunity, if not
321058 -     requirement, exists to authenticate those who participate.  No,
321059 -     I'm not talking about private exclusive NICs; anybody can join,
321060 -     but they must be authentic, and tracable, because the links can be
321061 -     traced, through logs, to individuals, and that's probably the way
321062 -     things should be. ref DRT 1 00HS
321063 -
321065 -  ..
321066 - Law Protects Property Rights
321067 -
321068 - Jack indicates there are legal implications from third parties
321069 - creating links to original work without permission, which BrowseUp
321070 - seems to support. ref DRT 1 00BS
321071 -
321072 - He understands that eBay got an injunction against a dotCom that was
321073 - either linking or transcluding auction information at the dotCom's web
321074 - site.
321076 -  ..
321077 - A search on the web using Google for 'deep linking' got 224,000 hits.
321079 -  ..
321080 - The second hit.....
321081 -
321082 -
321083 -       http://davenet.userland.com/1999/08/09/deepLinking
321084 -
321085 -
321086 - ....returned an article published by wired.com that says in part....
321087 -
321088 -       "Legal experts did comment, however, saying the legal landscape
321089 -       surrounding deep linking, or hyperlinking deep into another's
321090 -       Web page, is fraught with unpaved ways." ref DRT 1 GK4F
321091 -
321092 -
321093 -
321094 -
321095 -
321096 -
321097 -
321098 -
321099 -
321100 -
321101 -