Annotation of bookie/www/purpose.html, revision 1.4

1.1       will        1: Bookie is a personal attempt to keep the bookmarks that I have at home
1.4     ! will        2: synced with the bookmarks I have at work, and also to have shared bookmarks.  
        !             3: 
        !             4: It is an outgrowth of the bluesky <a
1.1       will        5: href="http://www.mozilla.org/blue-sky/ui/199805/bookmarks.html">good
                      6: bookmarking</a> and <a
                      7: href="http://www.mozilla.org/blue-sky/misc/199805/collaborative-bookmark-index.html">collaborative
                      8: bookmark indexing</a>.  In addition, there are sites which attack this
1.4     ! will        9: problem from another angle: 
        !            10: <a href="http://renaghan.com/bookmarker/">Bookmarker</a> and 
        !            11: <a href="http://www.webwizards.net/useful/wbbm.htm">Web-Based Bookmark Managers</a>.
1.1       will       12: 
                     13: <p>Quite frankly, bookmark management sucks.  Every person I know has a
                     14: collection of bookmarks which have grown over months if not years.  Not only
                     15: the bookmarks themselves but the structure of the bookmark directory is
                     16: critical.  Yahoo's origin and real, underlying purpose is as a huge
                     17: collection of well organized bookmarks.  Yet while it is easy to send a URL
                     18: over the web, sending branches or entire trees is impossible.  It is
                     19: impossible to share the same bookmarks folder with several people, so that
                     20: all information can be synced over a department.  And it's really hard to
                     21: keep bookmarks synced between several locations.
                     22: 
                     23: <p>The roaming access feature in Netscape goes in the right direction of
                     24: solving these problems, but RDF is the perfect answer to these problems.
                     25: Whenever a browser wants to see bookmarks, it can make a request to a
                     26: central bookmark server, and receive streamed RDF.  Likewise, whenever a
                     27: bookmark or branch is submitted, RDF can be sent to the server and synced
                     28: with all the other clients.
                     29: 
1.2       will       30: <p> Of course, this is barely scratching the surface of what Bookie could do.
                     31: 
                     32: <p>It could invalidate useless bookmarks.
                     33:  
                     34: <p>It could keep private bookmark folders which you could only see by
                     35: typing a password. 
                     36: 
                     37: <p>It could provide folders with multiple parents so that you could have the 
                     38: equivalent of symlinks in folders. 
                     39: 
                     40: <p>It could rearrange or delete bookmarks according to your own criteria. 
                     41: 
                     42: <P>You could have limited access to bookie allowing you to add only
1.1       will       43: annotations to a bookmark, or submit links on an honor system so that the
1.2       will       44: most popular float to the top.  (See 
1.3       will       45: <a href="http://www.ilrt.bris.ac.uk/discovery/2000/09/rudolf/recommender.html">this paper</a>
1.2       will       46: for more information).
                     47: 
                     48: <p>You could adjust your filter so that only the oldest or the newest bookmarks 
                     49: show up.
1.1       will       50: 

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>