Less is More (Branching WebPages to Increase Relevancy)
Let’s assume I’m looking for “Asynchronous processing support in Servlet 3.0″. I navigate my browser to Google and type “asynchronous support servlet 3.0″. I pick an interesting (arbitrary) article from the search results. Suppose I consider some of the introduction irrelevant to me (I might be an expert on the background concepts). However, the article might still be very interesting. So, what I would like to do is bookmark a page without the introduction and the background concepts. Unfortunately, this web page doesn’t let me remove some of its content. The best thing I could do is submit a comment, so the author might remove some of the content. Most likely the author would just ignore my comment and leave the article as it is. What I’d like to do is tune that article, so that next time I won’t have to search within the page for the relevant information.
Web 2.0 applications involve users to improve their website. For example Wikipedia allows everybody with knowledge on a subject to improve the quality of its content. In the case of Wikipedia, the joint effort of a group of people results in valuable content. Whenever a arbitrary individual feels like the content of an article is incorrect, he is not restricted to modify its content.
Most web pages need some sort of restriction. For example, you wouldn’t want your customers to change the contents of your web store like they change articles on Wikipedia. However, deleting content doesn’t make all information incorrect, it just hides a part of the information. In some cases it might even hide information that is irrelevant to the end user. Even better, something I consider unuseful might also be unuseful to my neighbor (saving a local search optimization).
So, deleting information from a page and bookmarking it, might help a subsequent visitor. Obviously you wouldn’t want your original content to be deleted by a visitor of your website. So giving your visitor the opportunity to make a branch of the web page where he can delete the content could help him to create a more appropriate view. The view -with some traceability to the original document- could then be shared with others who could benefit from it. My guess is that a document with a higher information density is more likely to be found by a search engine. The term frequency nor the number of relevant documents increases, but the information becomes more dense (keyword distance might increase). The weight of keyword within a document might increase as soon as a visitor deletes irrelevant content.
Let’s just hope there will be an API someday to enable web pages to save a local search.

May 5th, 2009 | by Rino | Tags: