First, there was the browser, and it was good. Then the browser got old, and something more was needed. People came up with a way to create easily, and it was good. Now, many create, yet not many navigate. Web 2.0 has difficulties scaling.
The concept of a portal page is very Web 1.0. A portal points (for the most part) to content that someone else has deemed important. At best, you have given the portal a list of things you like and dislike, and the portal tailors the options based on that. It’s not enough.
The portal personalization solution currently used focuses on metadata. It simplifies what you, the reader, wants down to a simple list. A list that you (generally) actively create. This same option is used in more Web 2.0 applications as well. When you read this, you will notice that I have placed this article in a collection of categories (or tags). I have assigned metadata to this entry for the simple fact that this metadata enables others to more easily reach my data.
I could wax on about metadata for quite some time, but the point has been made. People use it constantly, but they have to make it. Why? If I am writing a blog entry, why should I need to provide an “abstract” of what content exists in the entry? Because, the ways that people find my site are directly based upon that metadata. We live in a metadata age.
Metadata isn’t going anywhere for quite some time. I’m going to be so bold as to say that until metadata isn’t the primary way that people find and use content on the internet, it will still be the age of Web 2.0, regardless of what the actual label used is.
Web 3.0 is going to be immersive, not immersive like a 3-D environment is (that would be, at least at this point, unusable), but like a good conversation witha friend is. Web 3.0 will have the conversations of Web 2.0, but it will approach these conversations differently. Web 3.0 will be focused on data.
The actual content of this entry is important, otherwise I would simply have an entry that said, “I am currently thinking about Web 3.0, data, and metadata.” The comments would be metadata too. So, instead of “You are an idiot,” we would get “personal_comment.” What I am describing is unfair; labeling systems have been around almost as long as the written word. They aren’t going anywhere.
What I am saying is that the metadata should be almost invisible. An outside source should look at this entry (and not realize that it is barely coherent drivel) and determine what the article is about. It should see a reader that spends an inordinate amount of time looking at “big picture” discussions of metadata and data and recommend that the reader look at this entry. The reader shouldn’t have to say tthat he or she has an interest in metadata vs. data.
I suspect that something along the lines of what I am suggesting would not be a web application itself, but a modification of the browser. The browser should “learn” what a user likes (although it must have an “ignore this site” option somewhere) and present other sites that the user would find interesting without any intervention.
One web site ha sthe groundwork fairly done for the true “data” system, Google. If they were ever to come out with a Google Browse (and if they use that name, I want money or a job), I would expect it to work much like I’ve described.