ReadWriteWeb

It's the end of 2008 and everyone on the Web is hurting due to the economy. But we know that things will get better, because slow-downs eventually bury the old and give birth to new evolutionary ways of doing things.

One of these evolutions started quietly in 2008. We are witnessing the rise of a new kind of web: contextual. You might not have heard or thought about it much yet, but you are already using it today. Search remains the killer app on the web, but context is quickly become a viable contender. Why? Because context is what happens instead of search.

What Is The Contextual Web?

Until recently on the web, most sites have not been software - only data, a bunch of flat HTML pages. The software that you used to look at them was, of course, the web browser. The problem was that the browser had no idea what the pages contained, and it did not know what you were doing. Because the browser could not infer your context, it could not help you explore related and relevant information.

The contextual web experience is fundamentally different because there is an understanding of what the user is doing. The combination of the information on the page and the user's behavior creates the context. Once you understand the user's context, you can be more helpful. So, contextual technologies have the potential to bite into the pie that today belongs to search, because it is able to bypass search.

Consider the difference between looking at the IBM home page and a movie page on Netflix. The context is very different, and so likely is the user's intention. The user may be looking at IBM because she is looking for a job or researching IBM products. When the user is looking up a movie, it is because she is thinking about renting it.

The Key Properties of The Contextual Web

The Contextual web will happen when browsers and websites evolve to recognize what users are trying to do. It is the web with less choice and more meaning, where instead of Googling all the time, we Google once and then the rest of the information is available to us automatically, based on our current context.

Here are the key properties of the contextual web experience:

  • Relevancy: understanding the user's context better drives content relevancy.
  • Shortcuts: contextual shortcuts reduce the need for raw search.
  • Personalization: context is based on user intentions and history.
  • Remixing: relevant information from around the web is instantly available.

What are some specific examples of contextual technologies that are improving our web experience right now?

Markup Technologies

One of the keys to inferring user context is understanding the underlying information that the user is looking at. This is why the contextual web is related to -- and, to be more precise, is powered by -- semantic web. We have written a lot here on ReadWriteWeb about semantic technologies. Notably, we discussed the difference between the top-down and bottom-up approaches to semantic web, both of which are important for understanding the contextual web.

The bottom-up approach to context is about annotating pages. For example, all modern browsers can detect if the page you are looking at contains an RSS feed. This happens because the browser looks for a tag in the head of the page, which declares type . The fact that the page offers an RSS feed creates an obvious context: subscription. So, the browser then invites you to subscribe using your favorite RSS reader.

Another form of markup that has been discussed recently is microformats, which offer an XHTML-compliant way of embedding metadata about people, places, events, and reviews in existing web pages. Even though microformats are not ubiquitous today, there are clear benefits to using them. The image below is from an excellent post by Mozilla UI lead Alex Faaborg about leveraging microformats in the browser.

Building on the hAtom microformat are Web Slices, introduced by Microsoft in Internet Explorer 8. Web Slices enable publishers to notify users when the information in their web pages changes. For example, Weather.com can create a Web Slice that tells the user when a local weather update is available. eBay can deliver a Web Slice that notifies the user when the price of an auction changes. Similar in concept to RSS, Web Slices focus on updates in part of the web page, enabling publishers and users to communicate directly via the browser.

There are other markup formats that help provide context. For example, popular add-on Cooliris offers a markup format for signaling that a site contains images. By placing a bit of XML code in their home directory, site owners enable users to experience their images using the stunning 3D visualization developed by Cooliris. Another markup format, developed by AdaptiveBlue [disclosure: this is the company I founded], is called ABMeta. This format allows publishers to annotate pages that contain information about books, music, movies, wine, restaurants, stocks, and other everyday things.

All of these markup-based approaches face the same issue: publishers have to do the work of actually annotating the pages. And while the semantic web community has been very vocal about the benefits of annotation, the majority of the web is still flat HTML.

Page 2: Widgets

Page:  1   2   3  Next  »


RWW SPONSORS



ReadWriteCloud - Sponsored by VMware and Intel
Visit ReadWriteWeb's new developer channel, ReadWriteHack, sponsored by Intel Atom Developer Program






RWW PARTNERS
Recommended Story