A web browser which loads web sites that are not documents, but components, forms, and widgets.
HTML is extremely document based. Complex and even simple websites sometimes find HTML is perfect for documentation, but not for application.
A component based browser will load GUI widgets like an executable application loads them. There will be no document base. The Component Based Websites will use forms instead of documents. (pixel positioning versus document/html style positioning)
A component based browser will be backward compatible with HTML websites. When the component based browser detects an HTML based page or website, it will load the website as so.
A component based browser will also help reduce the need for ridiculous concoctions such as JavaScript and VBScript. It may also help reduce the number of thin clients out there, and ease the development of thin clients. Developing an application inside a component based web browser won't be a sin, unlike HTML based web applications (who lack functionality, and act clunky).
How will search engines parse and index component based websites?
They will learn to parse them.
Much of the component based websites will have a combination of documents and applications. Most likely the search engines will only want to parse the documents, and leave the applications basically alone (maybe parse some text from the applications.). With Component Based Browsers, we will have to figure a way to make a parsable site map for the search engines to crawl, if for example some documents are embedded in the component based browser application.
A website owner can still tell people about his/her component based websites from an HTML page, and lead people into the application through a hyperlink. For example, use HTML as your introduction or initial instruction page. Lead people into your web applications. Just like someone would advertise a software program to you on a website, and then you would download it. A component based website would offer you details or an introduction about the web application, and then you would load the application from a hyperlink immediately. This is faster than downloading some sort of thin client, which you have to install, set up, etc.
It seems the current search engines can't parse HTML very well anyway. You may beg to differ since you find relevant results, but the fact is you are only seeing 10 or 1 percent of all the websites out there. How do we know this? Out of 5 domains I've owned, I've never had more than 5-10 percent of the total pages visible on the search engine at one time. This applies mainly to medium size sites and larger though - some of the smaller sites will in fact get indexed competely. Many people claim the same, on several search engine discussion forums. --L505
Search engines seem to have enough trouble with HTML as it is. The claim that link based documents (html) is easy to parse for search engines is still a mystery. Why then, does Google, MSN search, and Yahoo search not contain even %10 of the internet? This wiki for example, has been up for several months, and not even %5 of the pages are indexed on Google (as of September/August 2005).
|
