Overview
LINX
DRAFT STATUS – I typed and proofread as I went – since
this is mainly for fun, please ignore the obvious (to you) errors. cdb
For at least the past two years I’ve wanted a centralized way to store and organize the little snippets of information we typically call bookmarks. Ever since I had two computers that I used to browse the web I’ve hit the favorites button to capture that little token that would provide a remembrance of visits to all those special places. Having more than one place to save those tokens has created a problem for me on more than one occasion like the night I was at home doing some late night research only to remember the next day on the plane that “my links” where at home. Many times I’ve resorted to the “email myself “ trick to get the info to all the various places that I want it. But what I’ve really desired is a magical way to pull all the snippets into one collection. LINX is a crude start to that longing.
Besides, I wanted to have a data driven prototype that could be used to play with and test all the newest web methods and protocols. Also, I wanted something that could be shared publicly without any association of prior projects. And anyway, saving bookmarks is natural for me. I’m going to create the links and use the links so if in the mean time I can create some tools to coalesce, manipulate and animate the processing then everything is so much better.
My friends (esp. Miss July 4th) laugh at my attempts to clean up and organize “stuff”. Basically, I use the extremely effective (for me) method of clutter/pile organization. “Don’t worry I can find it” is a typical phase people like me use. You’ve seen us, our desk is the messiest in the office (mind you, I’m not saying dirtiest.) I think “clean office” people use this as another form of discrimination. But I digress…
The set of prototypes is called LINX. When programming I always want a small name for the system because you have to type it so many times. I started with bookmarks and mymarks and bm(that one didn’t seem too appealing) and finally started into synonyms like favorites and links. And, then I shorten that to LINX. Also being the marketer, I wanted something that could have a neat graphic associated with it. Isn’t a linx a bobcat? No, my spell checker just informed me that the animal is called a lynx (and so you also know that spelling is another challenge for me.) Anyway, I didn’t create a bobcat like graphic I blew the whole think by creating a chain of links. Next time I think I call it MARX (and I claim the Ô on that if it isn’t already taken.)
LINX is a loosely coupled set of prototypes for testing and demonstrating web technologies that revolve around a system that managing bookmarks (Netscape) or favorites (Microsoft).
LINX will manage bookmark links to various important websites/pages. (Solely the contributor determines Importance or relevance.) Mechanisms for accumulating, storing, displaying, organizing, and synchronizing the links will be enabled. The potential for private, public and group access will be considered during development although may not be completely implemented until later.
Bookmark links will be contributed from client computers. Storage and formatting will occur from the server. Several different means of contribution may be covered including: 1) bulk loading from existing favorites directory or bookmark files, 2) browser function (Java, JavaScript or VBScript) or 3) add-on to IE. Organization/maintenance will occur through web pages/forms or a fat client tool. Formatting will begin on the server with content displayed on the client (browser) using many techniques. (Flexibility in display is one of the main objectives of the prototypes. Refer to the prototype for the most current capabilities in this area.)
n Synchronization of multiple systems that are all contributing to the same collection (tree) of bookmarks
n Ability to add new links to existing central data store – easily & with limited preparation required. Links should be contributed from main systems (where permanent tools can be installed) and borrowed systems (where “no trace” can be left of the use of that system.)
n Organization will require simple methods to manipulate the collection (tree) of links. This will include adding new folders, sorting, deleting, editing, etc.
n Security – User authentication
n Technically how to maintain a tree/hierarchy of data (low level – but something I’m interested in.)
n Architecture for the display of the web pages with a “nice” look.
The prototypes will eventually include most of the following technologies:
n Server side technologies:
n ASP
n VBScript
n JavaScript
n Server components
n ADO & databases
n Client side technologies
n HTML
n DHTML
n VBScript
n JavaScript
n Java
n IE components/add-ons
n Fat client
n RDS
n Protocols
n XML
n XSL
n Style Sheets
LINX includes prototypes/programs and documents that describe additional components of the system. Refer to those for additional information.
n Ability to log events – such as creation, revision, etc
n Use redirection for visitors/guests so that accurate reference activity/information can be collected.
n Use of the link trees to create activity reports – such as traffic at that site or location in search engine or collecting keywords – perhaps filtering the targets for synopsis of information.
n Link – Status – Date created, last visited, broken link status, static/dynamic etc.
n Expand LINX to include general relational information such as categorization of products, relationship to partners and competitors, references to products/services/information, contact information such as employees (CEO, CIO, VPs, PR, Directors, sales people) and references to people with their associations (interests, areas of expertise, employment) the idea being that all cross-references would also be listed.
LINX was created to demonstrate technologies that interest Strategy1st. This should not be construed as a complete display of expertise of Strategy1st. The prototypes are limited in purpose, capability and completeness and have only been created as experiments. Furthermore, the prototypes are a work-in-progress, so what has been described may not reflect the actual system at any specific time.